Triple
T13678569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Johns |
E327938
|
entity |
| Predicate | immortalNumber |
P73066
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Andrew Johns, immortalNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immortalNumber Context triple: [Andrew Johns, immortalNumber, 8]
-
A.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
-
B.
numberInMyth
chosen
Indicates that a given number appears with some significance or role within a particular myth or mythological narrative.
-
C.
immortality
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
D.
magicNumber
Indicates that an entity is a special constant or value with a particular, often hidden or predefined, significance within a system or context.
-
E.
famousNumber
Indicates that a number is widely recognized or notable for a particular reason, property, or occurrence.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65d8dc081909664e69bb38610ba |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.