Triple
T10324030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricky "Jupe" Park |
E242712
|
entity |
| Predicate | relationshipToEntity |
P84787
|
FINISHED |
| Object | neighbor of Haywood ranch |
—
|
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: neighbor of Haywood ranch | Statement: [Ricky "Jupe" Park, relationshipToEntity, neighbor of Haywood ranch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToEntity Context triple: [Ricky "Jupe" Park, relationshipToEntity, neighbor of Haywood ranch]
-
A.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
B.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
subjectRelation
chosen
Indicates that one entity stands in a specified relational role or connection to another entity.
-
D.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
E.
relationshipEnd
Indicates that a previously existing relationship between entities has been terminated or has come to an end.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.