Triple
T3938794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Managua |
E90980
|
entity |
| Predicate | usedInDatabases |
P52665
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [America/Managua, usedInDatabases, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDatabases Context triple: [America/Managua, usedInDatabases, yes]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
statusInDatabases
Indicates the current state or condition an entity has within one or more database systems.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
- F. None of above. chosen
Provenance (4 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfb12b88190a6ca6574b1aadb6e |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeed3260cc8190bf294bdab507b1f9 |
completed | March 9, 2026, 3:54 p.m. |
Created at: March 9, 2026, 3:24 p.m.