Triple
T4229270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Merida |
E94536
|
entity |
| Predicate | databaseKeyType |
P21838
|
FINISHED |
| Object | string identifier |
—
|
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: string identifier | Statement: [America/Merida, databaseKeyType, string identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: databaseKeyType Context triple: [America/Merida, databaseKeyType, string identifier]
-
A.
databaseKey
Indicates that one entity serves as a unique key or identifier for accessing or referencing another entity within a database.
-
B.
keyType
chosen
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
databaseType
Indicates the specific kind or category of database technology associated with an entity.
-
D.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
E.
keyField
Indicates that the referenced field serves as a primary or unique identifier within a data structure or record.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e61ccc081909b880baf1d6a0f24 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.