Triple
T11446140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps Drive |
E271268
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Asan-Maina |
E903188
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Asan-Maina | Statement: [Marine Corps Drive, connects, Asan-Maina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asan-Maina Context triple: [Marine Corps Drive, connects, Asan-Maina]
-
A.
Asan-Maina
chosen
Asan-Maina is a village municipality on the western coast of Guam, known for its historical significance in World War II and proximity to the island’s capital, Hagåtña.
-
B.
Asanina
Asanina is a Byzantine noble family name associated with the influential Asen (Asan) dynasty.
-
C.
Asan
Asan is a city in South Korea known for its hot springs, historical sites, and growing role as an industrial and educational center.
-
D.
Barshaini
Barshaini is a small Himalayan village in Himachal Pradesh, India, that serves as a popular base and trailhead for treks into the Parvati Valley and surrounding high-altitude landscapes.
-
E.
Asmat
Asmat is a town located in the Anseba region of Eritrea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d81c6d4890819082fb4a670feb2629 |
completed | April 9, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5d3bdafb08190aadf5d63facfedaf |
completed | April 20, 2026, 7:20 a.m. |
Created at: April 8, 2026, 9:35 p.m.