Triple
T35865433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Stevenson |
E1037072
|
entity |
| Predicate | mayBeReferencedAs |
P92520
|
FINISHED |
| Object | John Stephenson |
—
|
NE NERFINISHED |
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: John Stephenson | Statement: [John Stevenson, mayBeReferencedAs, John Stephenson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeReferencedAs Context triple: [John Stevenson, mayBeReferencedAs, John Stephenson]
-
A.
nameMayReferTo
chosen
Indicates that a given name or label can ambiguously denote or be used for one or more possible entities.
-
B.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
C.
isReferencedAlongWith
Indicates that one entity is mentioned or cited together with another entity in the same context or reference.
-
D.
mayBeRegisteredAs
Indicates that an entity has the possibility or eligibility to be formally registered under a particular status, category, or registry.
-
E.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:06 p.m.