Triple
T2227069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb Guard |
E48675
|
entity |
| Predicate | continuousGuardingBegan |
P21276
|
FINISHED |
| Object | 1937 |
—
|
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: 1937 | Statement: [Tomb Guard, continuousGuardingBegan, 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousGuardingBegan Context triple: [Tomb Guard, continuousGuardingBegan, 1937]
-
A.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
patrolledBy
chosen
Indicates that an area, route, or domain is regularly monitored or guarded by a specific agent or group.
-
C.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
D.
protectedGround
Indicates that one entity has taken action to safeguard or defend another entity or area from harm, damage, or unauthorized interference.
-
E.
detentionOperationsBegan
Indicates that the process or activities related to detaining individuals were initiated or commenced.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0411e388190b35e82ad6688bfe3 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.