Triple
T17037944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden Tomb |
E413368
|
entity |
| Predicate | signageStates |
P125606
|
FINISHED |
| Object | “He is not here, for He is risen” |
—
|
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: “He is not here, for He is risen” | Statement: [Garden Tomb, signageStates, “He is not here, for He is risen”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signageStates Context triple: [Garden Tomb, signageStates, “He is not here, for He is risen”]
-
A.
signageStatus
Indicates the current condition or state of a sign or signage (e.g., present, missing, damaged, or updated).
-
B.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
C.
stateEnsign
Indicates that an entity holds the naval rank or position of an ensign within a particular state or governmental context.
-
D.
sponsorStates
Indicates that one entity acts as a sponsor or supporting state for another entity, typically providing backing, endorsement, or resources.
-
E.
conventionState
Indicates that an entity is in a particular formal status or phase within a convention or agreed procedural framework.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f45f84819092cfb27cc33da026 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.