Triple
T36493417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya coastal trade network |
E899112
|
entity |
| Predicate | hadNodeType |
P1595
|
FINISHED |
| Object | port city |
—
|
LITERAL 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: port city | Statement: [Maya coastal trade network, hadNodeType, port city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNodeType Context triple: [Maya coastal trade network, hadNodeType, port city]
-
A.
hasNodeType
chosen
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
-
B.
hasNode
Indicates that one entity contains, includes, or is associated with a particular node as part of its structure or composition.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hadModel
Indicates that an entity possessed, used, or was associated with a particular model (e.g., a product, design, or version) at some point in time.
-
E.
hadBranchIn
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
- F. None of above.
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.