Triple
T33610520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Man |
E860974
|
entity |
| Predicate | includesReferenceTo |
P8581
|
FINISHED |
| Object | Nelson Mandela |
E9390
|
NE 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: Nelson Mandela | Statement: [Mortal Man, includesReferenceTo, Nelson Mandela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesReferenceTo Context triple: [Mortal Man, includesReferenceTo, Nelson Mandela]
-
A.
isReferencedIn
chosen
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
B.
hasReferences
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
-
C.
isReferencedAlongWith
Indicates that one entity is mentioned or cited together with another entity in the same context or reference.
-
D.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
E.
requiresReferent
Indicates that one entity depends on or must reference another specific entity in order to be valid, interpretable, or complete.
- F. None of above.
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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0332a08b48819094aaed6e04a36886 |
completed | May 12, 2026, 2:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36119dbe8c8190aca70b690176b802 |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a0331998a688190b5d919697d4231ac |
completed | May 12, 2026, 1:56 p.m. |
Created at: May 1, 2026, 1:41 a.m.