Triple
T10129863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzanne Farrington |
E226307
|
entity |
| Predicate | keptDistanceFrom |
P56200
|
FINISHED |
| Object | film industry |
—
|
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: film industry | Statement: [Suzanne Farrington, keptDistanceFrom, film industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptDistanceFrom Context triple: [Suzanne Farrington, keptDistanceFrom, film industry]
-
A.
distancedFrom
chosen
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
awayFrom
Indicates that one entity is located at a distance from, or moving farther away from, another entity.
-
D.
minimumDistanceRequirement
Indicates that there is a required minimum distance that must be maintained between the related entities.
-
E.
hasApproximateDrivingDistanceFrom
Indicates that one entity is located at an estimated or approximate driving distance from another entity, typically measured along road routes rather than as a precise or exact value.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd33438988190be45878f98695816 |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.