Triple
T35364643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burg Stargard |
E1021595
|
entity |
| Predicate | castleInstance |
P101962
|
FINISHED |
| Object | Burg Stargard castle |
—
|
NE NERFINISHED |
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: Burg Stargard castle | Statement: [Burg Stargard, castleInstance, Burg Stargard castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleInstance Context triple: [Burg Stargard, castleInstance, Burg Stargard castle]
-
A.
castlePosition
Indicates the spatial location or placement of a castle relative to a reference point or area.
-
B.
castleFunction
Indicates the primary role, purpose, or use that a castle serves (e.g., defense, residence, administration, or symbolism).
-
C.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
D.
castle
chosen
Indicates that one entity is a castle associated with, located at, or serving as the stronghold or residence for another entity.
-
E.
castleName
Indicates that an entity has the specified name of a castle.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.