Triple
T20720081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cléante |
E509286
|
entity |
| Predicate | hasRelationshipTypeWithArgan |
P33476
|
FINISHED |
| Object | prospective son-in-law |
—
|
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: prospective son-in-law | Statement: [Cléante, hasRelationshipTypeWithArgan, prospective son-in-law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipTypeWithArgan Context triple: [Cléante, hasRelationshipTypeWithArgan, prospective son-in-law]
-
A.
hasRelationshipTypeWithOmar
Indicates that an entity stands in a specified type of interpersonal or associative relationship with Omar.
-
B.
hasRelationshipTypeWithNenaDaconte
Indicates that there exists a specific type of relationship between an entity and Nena Daconte.
-
C.
hasRelationshipTypeWith Valère
Indicates that an entity stands in a specific, characterized type of relationship with Valère.
-
D.
hasArcType
Indicates that one entity is associated with, or characterized by, a specific type or category of arc.
-
E.
hasRelation
chosen
Indicates that there exists some specified relationship or association between two 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d4de6c81908f8c98c2f1e70cc4 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:26 p.m.