Triple
T10330749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crest |
E242865
|
entity |
| Predicate | towerUseHistorical |
P93461
|
FINISHED |
| Object | 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: fortress | Statement: [Crest, towerUseHistorical, fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerUseHistorical Context triple: [Crest, towerUseHistorical, fortress]
-
A.
towerDatingFrom
Indicates that a tower originates from, or was constructed in, a specified time period or date.
-
B.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
C.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
D.
historicalServiceNear
Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
-
E.
historicalLevel
Indicates the degree or extent to which something is related to, situated in, or characterized by a particular historical period or 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7fb77348190ac8ff887f6f03450 |
completed | April 7, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.