Triple
T24047217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Casimir |
E595555
|
entity |
| Predicate | currentPhysicalRemains |
P97204
|
FINISHED |
| Object | no standing fort structures |
—
|
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: no standing fort structures | Statement: [Fort Casimir, currentPhysicalRemains, no standing fort structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPhysicalRemains Context triple: [Fort Casimir, currentPhysicalRemains, no standing fort structures]
-
A.
hasPhysicalRemains
chosen
Indicates that an entity possesses or is associated with tangible, material remains or physical evidence of its existence.
-
B.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
-
C.
numberOfUnidentifiedRemains
Indicates the count of human remains that have not yet been identified in a given context or case.
-
D.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
E.
lastRemnantOf
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cd50648190b009e97e5be53e8b |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:17 p.m.