Triple
T34786358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Day |
E1002817
|
entity |
| Predicate | mayBeNotableAs |
P22
|
FINISHED |
| Object | various local public figures |
—
|
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: various local public figures | Statement: [Charles Day, mayBeNotableAs, various local public figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeNotableAs Context triple: [Charles Day, mayBeNotableAs, various local public figures]
-
A.
isNotable
Indicates that an entity is recognized as significant, prominent, or worthy of attention within a particular context or domain.
-
B.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
-
E.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 3:59 p.m.