Triple
T33859597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flames Across the Border |
E867885
|
entity |
| Predicate | hasBritishSubject |
P182790
|
FINISHED |
| Object | British Army |
—
|
NE NERFINISHED |
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: British Army | Statement: [Flames Across the Border, hasBritishSubject, British Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBritishSubject Context triple: [Flames Across the Border, hasBritishSubject, British Army]
-
A.
legalStatusUnderBritish
Indicates the legal status or classification an entity holds under British law or the British legal system.
-
B.
hasBritishAccent
Indicates that the subject speaks with a British accent.
-
C.
hasTypicalCitizenship
Indicates that an entity is generally or commonly a citizen of a specified country or jurisdiction.
-
D.
locatedInBritishCountry
Indicates that one entity is geographically or administratively situated within a country that is part of the United Kingdom.
-
E.
hasAncestralCitizenshipOf
Indicates that an entity holds or is recognized as holding citizenship of another entity based on ancestral or lineage connections rather than solely on birth or residence.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: May 1, 2026, 1:47 a.m.