Triple
T35507068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT7-2 |
E1026177
|
entity |
| Predicate | familyBasedOn |
P140995
|
FINISHED |
| Object | GE T700 |
—
|
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: GE T700 | Statement: [CT7-2, familyBasedOn, GE T700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyBasedOn Context triple: [CT7-2, familyBasedOn, GE T700]
-
A.
fatherBasedOn
Indicates a paternal relationship inferred from indirect or derived evidence rather than directly asserted.
-
B.
basedOnFamilyOf
chosen
Indicates that one entity is derived from, modeled after, or determined by the family, lineage, or familial characteristics of another entity.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
motherBasedOn
Indicates a maternal relationship where one entity is considered the mother of another based on inferred, indirect, or non-biological evidence or criteria.
-
E.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:04 p.m.