Triple
T31141962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Crump |
E793810
|
entity |
| Predicate | relativeIs |
P106099
|
FINISHED |
| Object | Phil Crump |
E1951236
|
NE 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: Phil Crump | Statement: [Jason Crump, relativeIs, Phil Crump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeIs Context triple: [Jason Crump, relativeIs, Phil Crump]
-
A.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
B.
isRelativeTo
chosen
Indicates that one entity has a familial or kinship relationship to another entity.
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
E.
relativeAlias
Indicates that one entity is known or referred to by an alternative name or label that is contextually related to another entity.
- F. None of above.
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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a296bccbd248190b5d04f0ccfec6f52 |
completed | June 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:06 p.m.