Triple
T15631366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The House That Landry Built |
E375819
|
entity |
| Predicate | associatedWithCoachRole |
P119524
|
FINISHED |
| Object | head coach |
—
|
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: head coach | Statement: [The House That Landry Built, associatedWithCoachRole, head coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCoachRole Context triple: [The House That Landry Built, associatedWithCoachRole, head coach]
-
A.
isActiveAsCoach
Indicates that an entity is currently functioning in the role of a coach within a given context or organization.
-
B.
basedInAsCoach
Indicates that a person holds a coaching position for an organization or team that is located in a specified place.
-
C.
requiresCoach
Indicates that one entity depends on or must have the involvement, guidance, or supervision of a coach in order for an action, process, or state to occur or be valid.
-
D.
trainerAssociation
Indicates a relationship where one entity serves as a trainer, coach, or instructor for another entity.
-
E.
associatedWithAdvisor
Indicates that an entity has a relationship of guidance, oversight, or mentorship with a designated advisor.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb536348190b93ed3c178d1ffb8 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.