Triple
T18101601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noel family |
E433231
|
entity |
| Predicate | landedFamily |
P130434
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Noel family, landedFamily, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landedFamily Context triple: [Noel family, landedFamily, yes]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
fareFamily
Indicates a relationship that classifies a fare or ticket into a specific fare family or category within a pricing structure.
-
C.
intendedFamily
Indicates that one entity is planned or designated to be part of another entity’s family or familial group in the future.
-
D.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
E.
capturedFamilyBy
Indicates that a family or family member has been taken into custody, control, or possession by another party.
- F. None of above. chosen
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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb6fed8819090798683353a5c08 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.