Triple
T26094494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Gleason |
E658222
|
entity |
| Predicate | hasMultipleReferents |
P29734
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Robert Gleason, hasMultipleReferents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleReferents Context triple: [Robert Gleason, hasMultipleReferents, true]
-
A.
canReferToMultipleIndividuals
chosen
Indicates that a single reference, term, or identifier may correspond to more than one individual rather than uniquely identifying just one.
-
B.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
C.
hasReferentKnownFor
Indicates that the referent (the thing being referred to) is known or notable for a particular characteristic, role, or achievement.
-
D.
hasMainReferent
Indicates that one entity serves as the primary or central referent for another entity within a given context.
-
E.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 7:50 p.m.