Triple
T27868505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein |
E704425
|
entity |
| Predicate | namedAfterInUniverse |
P170984
|
FINISHED |
| Object | Albert Einstein |
—
|
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: Albert Einstein | Statement: [Einstein, namedAfterInUniverse, Albert Einstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterInUniverse Context triple: [Einstein, namedAfterInUniverse, Albert Einstein]
-
A.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
inUniverseReference
Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
-
E.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
- F. None of above. chosen
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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 6:22 p.m.