Triple
T37664448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Guardian |
E937789
|
entity |
| Predicate | defendsStructure |
P6876
|
FINISHED |
| Object | Ocean monument |
—
|
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: Ocean monument | Statement: [Elder Guardian, defendsStructure, Ocean monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendsStructure Context triple: [Elder Guardian, defendsStructure, Ocean monument]
-
A.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
B.
shareDefenseStructure
Indicates that two or more entities utilize or are protected by the same defensive structure or system.
-
C.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
E.
providesDefence
Indicates that one entity offers protection or defensive support to another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:18 p.m.