Triple
T31262454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponderosa Ranch |
E797158
|
entity |
| Predicate | hasRealWorldReplica |
P16046
|
FINISHED |
| Object | Ponderosa Ranch theme park |
—
|
NE NERFINISHED |
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: Ponderosa Ranch theme park | Statement: [Ponderosa Ranch, hasRealWorldReplica, Ponderosa Ranch theme park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealWorldReplica Context triple: [Ponderosa Ranch, hasRealWorldReplica, Ponderosa Ranch theme park]
-
A.
hasRealWorldVersion
Indicates that something has a corresponding or equivalent version that exists in the real, physical world.
-
B.
hasRealModel
Indicates that an abstract, theoretical, or simplified entity is associated with a corresponding concrete or physically instantiated model in the real world.
-
C.
replicaOf
Indicates that one entity is an exact or near-exact copy of another entity, preserving its form, structure, or content.
-
D.
hasRealWorldOrigin
Indicates that something is derived from, based on, or directly connected to an actual entity, event, or source in the real world.
-
E.
hasReplicaDisplays
chosen
Indicates that an entity features or presents one or more replica items as displays.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
Created at: April 29, 2026, 9:12 p.m.