Triple
T5010113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nine Billion Names of God |
E112596
|
entity |
| Predicate | hasKeyObject |
P5510
|
FINISHED |
| Object | electronic computer |
—
|
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: electronic computer | Statement: [The Nine Billion Names of God, hasKeyObject, electronic computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyObject Context triple: [The Nine Billion Names of God, hasKeyObject, electronic computer]
-
A.
hasObject
chosen
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
B.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
C.
hasKeyDocument
Indicates that an entity possesses or is associated with a primary or essential document relevant to a particular context or process.
-
D.
hasKeyResource
Indicates that an entity possesses or depends on a critical resource necessary for its function, operation, or success.
-
E.
hasKeyImage
Indicates that one entity is designated as the primary or representative image associated with 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730bdb208190bebd7f22839ab6e5 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.