Triple
T8140772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin |
E190089
|
entity |
| Predicate | relationshipToCandide |
P80896
|
FINISHED |
| Object | traveling companion |
—
|
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: traveling companion | Statement: [Martin, relationshipToCandide, traveling companion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCandide Context triple: [Martin, relationshipToCandide, traveling companion]
-
A.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
relationshipToCatherine
Indicates the specific familial, social, or interpersonal connection that one entity has to the person named Catherine.
-
D.
relationshipPlannedWith
Indicates that a relationship between two entities has been intentionally arranged or scheduled to occur in the future.
-
E.
associatedWithCandidate
Indicates that there is a connection or relationship between an entity and a specific candidate, without specifying the nature or strength of that connection.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4442299881909db56f7475cbb99a |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39d20e78819092ea9e04357be008 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:36 p.m.