Triple
T37664233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean Temple |
E937784
|
entity |
| Predicate | isUniquePerStructure |
P8937
|
FINISHED |
| Object | three Elder Guardians per 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: three Elder Guardians per monument | Statement: [Ocean Temple, isUniquePerStructure, three Elder Guardians per monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUniquePerStructure Context triple: [Ocean Temple, isUniquePerStructure, three Elder Guardians per monument]
-
A.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
B.
isUniqueTo
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
C.
isUniqueWithinSystem
chosen
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
-
D.
isNonUniqueGlobally
Indicates that the referenced item is not guaranteed to be unique across the entire global scope or system.
-
E.
hasUniqueness
Indicates that something possesses a distinctive or one-of-a-kind quality that sets it apart from others.
- 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_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.