Triple
T4673861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norham |
E103628
|
entity |
| Predicate | castleType |
P43483
|
FINISHED |
| Object | medieval fortress |
—
|
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: medieval fortress | Statement: [Norham, castleType, medieval fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleType Context triple: [Norham, castleType, medieval fortress]
-
A.
castlePosition
Indicates the spatial location or placement of a castle relative to a reference point or area.
-
B.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
C.
castleOverlooks
Indicates that a castle is positioned so that it has a clear, elevated view over a particular area, object, or landscape.
-
D.
hasCastleType
chosen
Indicates that an entity is associated with, characterized by, or classified as a specific type of castle.
-
E.
hasCastle
Indicates that one entity possesses, controls, or contains 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.