Triple
T925250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Life |
E19968
|
entity |
| Predicate | statusOfNames |
P19196
|
FINISHED |
| Object | names can be written |
—
|
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: names can be written | Statement: [Book of Life, statusOfNames, names can be written]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfNames Context triple: [Book of Life, statusOfNames, names can be written]
-
A.
nameStatus
chosen
Indicates the status or condition associated with an entity’s name, such as whether it is current, preferred, alternate, or deprecated.
-
B.
namesakeStatus
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
nationalRegisterStatus
Indicates whether an entity is listed, eligible, or otherwise classified within an official national register or registry.
-
E.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2970a4c8190b22cb2fd4706f62b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.