Triple
T34598471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Ward |
E888384
|
entity |
| Predicate | hasFamilyConnectionDepictedIn |
P7844
|
FINISHED |
| Object | The Fighter |
—
|
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: The Fighter | Statement: [George Ward, hasFamilyConnectionDepictedIn, The Fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyConnectionDepictedIn Context triple: [George Ward, hasFamilyConnectionDepictedIn, The Fighter]
-
A.
hasFictionalFamilyMember
Indicates that one entity has another entity as a family member within a fictional or imagined context.
-
B.
hasMainCastFamilyRelationship
Indicates that there is a family relationship between members of the main cast in a work (e.g., film, series, or play).
-
C.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
D.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
isFromFamilyKnownFor
Indicates that an entity belongs to a family that is widely recognized or notable for a particular characteristic, achievement, or reputation.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 1, 2026, 2:03 a.m.