Triple
T22498340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamps-lighting (Lucernarium) |
E556202
|
entity |
| Predicate | primarySymbolicAction |
P138041
|
FINISHED |
| Object | lighting of lamps |
—
|
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: lighting of lamps | Statement: [Lamps-lighting (Lucernarium), primarySymbolicAction, lighting of lamps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySymbolicAction Context triple: [Lamps-lighting (Lucernarium), primarySymbolicAction, lighting of lamps]
-
A.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
B.
initialAction
Indicates the first or starting action taken in a sequence of actions or events.
-
C.
significantAction
Indicates that an action taken by an entity is of notable importance or consequence within a given context or process.
-
D.
coreAction
chosen
Indicates the primary or central action that defines the main relationship or event occurring between the involved entities.
-
E.
primaryInteraction
Indicates the main or most significant interaction occurring between the involved entities.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb3deb88190874230ae06a352d6 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.