Triple
T37664395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Guardian |
E937788
|
entity |
| Predicate | spawnsCountPerMonument |
P190549
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Elder Guardian, spawnsCountPerMonument, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spawnsCountPerMonument Context triple: [Elder Guardian, spawnsCountPerMonument, 3]
-
A.
hasNumberOfMonuments
Indicates the specific count of monuments associated with or present in a given entity.
-
B.
isMonumentNumber
Indicates that one entity is the official monument identification number assigned to another entity.
-
C.
hasStoneMonument
Indicates that one entity possesses, contains, or features a stone monument associated with it.
-
D.
monumentGroup
Indicates that one monument belongs to, or is categorized within, a specific group or collection of monuments.
-
E.
knownMonuments
Indicates that an entity is recognized or identified as a monument by another entity or within a given context.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.