Triple
T23866533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vimy |
E592594
|
entity |
| Predicate | hasFederalStatus |
P23390
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [Vimy, hasFederalStatus, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFederalStatus Context triple: [Vimy, hasFederalStatus, active]
-
A.
federalStatus
chosen
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
-
B.
hasNationalStatus
Indicates that an entity possesses an official national-level designation, recognition, or status within a country.
-
C.
hasFederalElectorate
Indicates that an entity is associated with a specific federal electoral district that represents it in a national legislative body.
-
D.
hasFederalRecognitionStatus
Indicates whether an entity is officially recognized by a federal government authority and, if so, what that recognition status is.
-
E.
canBeFederalizedBy
Indicates that an entity has the legal or practical capacity to be brought under the authority, control, or jurisdiction of a specified federal-level entity.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae47b40819080d1c5294ee59066 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.