Triple
T14877878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rip |
E349913
|
entity |
| Predicate | relationshipTypeWithClay |
P10690
|
FINISHED |
| Object | friend |
—
|
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: friend | Statement: [Rip, relationshipTypeWithClay, friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithClay Context triple: [Rip, relationshipTypeWithClay, friend]
-
A.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
D.
relationshipCharacterizedAs
Indicates that one relationship is described, defined, or typified in terms of another specified characteristic or relational type.
-
E.
substrateRelationship
Indicates that one entity serves as a substrate upon which another entity acts, is processed, or depends in a functional relationship.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.