Triple
T17945127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddy |
E448683
|
entity |
| Predicate | relationshipToEd |
P129828
|
FINISHED |
| Object | friend and scam partner |
—
|
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 and scam partner | Statement: [Eddy, relationshipToEd, friend and scam partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToEd Context triple: [Eddy, relationshipToEd, friend and scam partner]
-
A.
relationshipToStudents
Indicates the type or nature of connection one entity has with students, such as role, affiliation, or responsibility toward them.
-
B.
relationshipToChildren
Indicates the type of familial or social connection an entity has to one or more children.
-
C.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
D.
relationshipToUniversity
Indicates the type or nature of a person's or entity's connection or affiliation with a specific university.
-
E.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad990b948190a5e6fd50a15f64e3 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.