Triple
T32064775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Smith (producer) |
E818845
|
entity |
| Predicate | nameDisambiguation |
P162430
|
FINISHED |
| Object | not the actor Will Smith |
—
|
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: not the actor Will Smith | Statement: [Will Smith (producer), nameDisambiguation, not the actor Will Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDisambiguation Context triple: [Will Smith (producer), nameDisambiguation, not the actor Will Smith]
-
A.
nameClarification
chosen
Indicates that an additional explanation or specification is provided to clarify an entity’s name or how it should be understood.
-
B.
nameDistinction
Indicates that two entities are distinguished from one another specifically by differences in their names.
-
C.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
D.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 12:22 a.m.