Triple
T29250616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viviane |
E741555
|
entity |
| Predicate | hasRelationshipTypeWithMerlin |
P201141
|
FINISHED |
| Object | teacher |
—
|
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: teacher | Statement: [Viviane, hasRelationshipTypeWithMerlin, teacher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipTypeWithMerlin Context triple: [Viviane, hasRelationshipTypeWithMerlin, teacher]
-
A.
hasRelationshipTypeWith Valère
Indicates that an entity stands in a specific, characterized type of relationship with Valère.
-
B.
hasCentralRelationshipType
Indicates that there exists a primary or most significant type of relationship that characterizes how two entities are related to each other.
-
C.
hasRelationshipTypeWithOmar
Indicates that an entity stands in a specified type of interpersonal or associative relationship with Omar.
-
D.
hasRelationshipTypeWithRocky
Indicates that an entity has a specific type of relationship or connection with the entity named Rocky.
-
E.
hasSymbolicRelationshipType
Indicates that there exists a symbolic (non-literal) relationship of a specified type between two entities.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
| PDg | Predicate description generation | batch_69ffcc60dae48190b76b3eb7e2ce5103 |
completed | May 10, 2026, 12:08 a.m. |
Created at: April 28, 2026, 12:34 p.m.