Triple
T26622606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Coffin III |
E668242
|
entity |
| Predicate | formerRelationshipType |
P143101
|
FINISHED |
| Object | roommate |
—
|
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: roommate | Statement: [Benjamin Coffin III, formerRelationshipType, roommate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerRelationshipType Context triple: [Benjamin Coffin III, formerRelationshipType, roommate]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
formerRelationshipStatus
chosen
Indicates that a relationship between entities existed in the past but no longer holds in the present.
-
C.
laterRelationshipWith
Indicates that one entity has a relationship with another that occurs at a later time relative to some reference point or prior relationship.
-
D.
establishedRelationship
Indicates that a formal, recognized relationship has been created and is now in effect between the referenced entities.
-
E.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 2:21 a.m.