Triple
T18841907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franzensfeste |
E460817
|
entity |
| Predicate | fortressOriginalFunction |
P133131
|
FINISHED |
| Object | military stronghold |
—
|
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: military stronghold | Statement: [Franzensfeste, fortressOriginalFunction, military stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortressOriginalFunction Context triple: [Franzensfeste, fortressOriginalFunction, military stronghold]
-
A.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
-
B.
modernFortressName
Indicates that an entity is known by a specific modern-era name as a fortress.
-
C.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
D.
fortressShape
Indicates that one entity has the physical form, outline, or structural configuration characteristic of a fortress.
-
E.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ea35c88190af6659551ad18130 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.