Triple
T19722378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumen |
E473642
|
entity |
| Predicate | nameInOriginalWork |
P137071
|
FINISHED |
| Object | Lumen in caelo |
—
|
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: Lumen in caelo | Statement: [Lumen, nameInOriginalWork, Lumen in caelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInOriginalWork Context triple: [Lumen, nameInOriginalWork, Lumen in caelo]
-
A.
nameInOriginalLanguage
Indicates that an entity’s name is given in its original or native language form.
-
B.
creatorNameInOriginalScript
Indicates that the relationship specifies the name of the creator written in the original script or writing system used by that creator.
-
C.
originalTitleOfWork
Indicates that one work is the original title under which another work was first created, published, or released.
-
D.
originalTitleAuthorName
Indicates that the associated name is the author of the work’s original title.
-
E.
authorOrigin
Indicates that an author has a specific place, region, or country as their origin or background.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f587d88190bf519fec7ce634d3 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.