Triple
T25093644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory City |
E628529
|
entity |
| Predicate | hasHistoricalElements |
P86463
|
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: [Victory City, hasHistoricalElements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalElements Context triple: [Victory City, hasHistoricalElements, yes]
-
A.
hasHistoricFeatures
chosen
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
D.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
E.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 6:24 a.m.