Triple
T8850961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhul-Kifl |
E210635
|
entity |
| Predicate | nameInterpretation |
P64940
|
FINISHED |
| Object | one who is given a double portion or share |
—
|
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: one who is given a double portion or share | Statement: [Dhul-Kifl, nameInterpretation, one who is given a double portion or share]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInterpretation Context triple: [Dhul-Kifl, nameInterpretation, one who is given a double portion or share]
-
A.
nameLiterallyMeans
chosen
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
B.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
C.
nameIndicates
Indicates that one entity’s name signifies, reveals, or is used to denote a particular property, identity, or characteristic of another entity.
-
D.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
E.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c2300c819097b1ca6ebe2f749a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.