Triple
T30024425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerco Pueblo |
E762840
|
entity |
| Predicate | interpretiveSignage |
P36768
|
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: [Puerco Pueblo, interpretiveSignage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretiveSignage Context triple: [Puerco Pueblo, interpretiveSignage, yes]
-
A.
hasInterpretiveSigns
chosen
Indicates that interpretive or informational signs are present at or associated with the subject.
-
B.
interpretiveInformation
Indicates that one entity provides explanatory or contextual information used to interpret, clarify, or make sense of another entity or its content.
-
C.
signInterpretation
Indicates that one entity provides or assigns a particular meaning, explanation, or reading to a given sign, symbol, or signal.
-
D.
hasInterpretiveExhibits
Indicates that an entity includes or provides exhibits designed to explain, interpret, or contextualize information for viewers.
-
E.
interpretationFacility
Indicates that an entity serves as a facility or venue where interpretation (such as language or translation services) is provided or supported.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 29, 2026, 6:48 p.m.