Triple
T22397578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy Muir |
E553674
|
entity |
| Predicate | notableRelationshipType |
P10690
|
FINISHED |
| Object | human–ghost relationship |
—
|
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: human–ghost relationship | Statement: [Lucy Muir, notableRelationshipType, human–ghost relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelationshipType Context triple: [Lucy Muir, notableRelationshipType, human–ghost relationship]
-
A.
notableRelativeType
Indicates the specific familial or relational role that a notable relative has in relation to the subject.
-
B.
notableRelationshipDynamic
Indicates a significant, distinguishing type of relationship or interaction that meaningfully shapes how the involved entities are connected or influence one another.
-
C.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
D.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
E.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585f67108190b8d3f23eaa0ed120 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:46 p.m.