Triple
T19148619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimì |
E468745
|
entity |
| Predicate | relationshipWithColline |
P134613
|
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: [Mimì, relationshipWithColline, friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithColline Context triple: [Mimì, relationshipWithColline, friend]
-
A.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
B.
belongsToLine
Indicates that an entity is a member or component of a particular line or linear grouping.
-
C.
relationshipWithAxis
Indicates a specified way in which something is oriented, aligned, or otherwise related with respect to a particular axis.
-
D.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
E.
angleRelation
Indicates a relationship specifying how two or more angles are related to each other, such as being equal, complementary, supplementary, or otherwise geometrically constrained.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97b48508190b61458821b6475ad |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.