Triple
T6334021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brand (Interstellar) |
E142446
|
entity |
| Predicate | relationshipToProfessorBrand |
P10690
|
FINISHED |
| Object | daughter |
—
|
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: daughter | Statement: [Brand (Interstellar), relationshipToProfessorBrand, daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToProfessorBrand Context triple: [Brand (Interstellar), relationshipToProfessorBrand, daughter]
-
A.
relationshipToUniversity
Indicates the type or nature of a person's or entity's connection or affiliation with a specific university.
-
B.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
associatedWithAdvisor
Indicates that an entity has a relationship of guidance, oversight, or mentorship with a designated advisor.
-
D.
roleAtInstitution
Indicates that an entity holds or has held a specific role or position within a particular institution.
-
E.
relationToExecutive
Indicates a relationship or connection that an entity has to an executive, such as reporting lines, oversight, or affiliation.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06549084c8190b73fd94c9e0cb302 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.