Triple
T3938789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Managua |
E90980
|
entity |
| Predicate | ianaIdentifierCase |
P52663
|
FINISHED |
| Object | case-sensitive |
—
|
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: case-sensitive | Statement: [America/Managua, ianaIdentifierCase, case-sensitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaIdentifierCase Context triple: [America/Managua, ianaIdentifierCase, case-sensitive]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
identifierStability
Indicates that an identifier maintains a consistent, unchanging reference to the same entity over time or across different contexts.
-
C.
isTraditionallyIdentifiedAs
Indicates that one entity is customarily or historically recognized or labeled as being the same as, or corresponding to, another entity.
-
D.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
E.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
- 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.