Triple
T2799858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islands and Lakes |
E53126
|
entity |
| Predicate | usesInterpretiveDisplays |
P36768
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Islands and Lakes, usesInterpretiveDisplays, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInterpretiveDisplays Context triple: [Islands and Lakes, usesInterpretiveDisplays, true]
-
A.
hasInterpretiveSigns
chosen
Indicates that interpretive or informational signs are present at or associated with the subject.
-
B.
hasInterpretiveExhibits
Indicates that an entity includes or provides exhibits designed to explain, interpret, or contextualize information for viewers.
-
C.
usesInterpretiveStaff
Indicates that an entity relies on interpretive staff (such as guides, educators, or docents) to convey information, context, or explanations about something to an audience.
-
D.
containsInterpretationOf
Indicates that one entity includes or embodies an interpretation or understanding of another entity.
-
E.
eraInterpreted
Indicates that one entity has been interpreted, understood, or given meaning by another 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.