Triple
T34175025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Square |
E876642
|
entity |
| Predicate | builtOnFormerMilitarySite |
P126626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Naval Square, builtOnFormerMilitarySite, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtOnFormerMilitarySite Context triple: [Naval Square, builtOnFormerMilitarySite, yes]
-
A.
formerMilitaryBase
chosen
Indicates that a location was previously used as a military base but no longer serves that function.
-
B.
isFormerMilitaryCenter
Indicates that a place previously served as a military center or base but no longer holds that function.
-
C.
hasFormerMilitaryInstallationNearby
Indicates that an entity is located close to a site where a military installation previously existed but is no longer active.
-
D.
hasNearbyMilitaryHistorySite
Indicates that an entity is located close to a site of historical military significance, such as a battlefield, fort, or memorial.
-
E.
wasMilitaryBaseDuring
Indicates that a location functioned as a military base during a specified time period or event.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:54 a.m.