Triple
T24616530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carabiniers (6th Dragoon Guards) |
E609276
|
entity |
| Predicate | raisedInCountry |
P118930
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [Carabiniers (6th Dragoon Guards), raisedInCountry, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedInCountry Context triple: [Carabiniers (6th Dragoon Guards), raisedInCountry, England]
-
A.
raisedIn
Indicates that an entity spent its formative or upbringing period within a particular place or environment.
-
B.
parentCountryOfOrigin
Indicates that one country is the original source or homeland from which another country historically emerged or originated.
-
C.
placeOfUpbringing
Indicates the location where an individual was raised or spent most of their formative years.
-
D.
laterCountryOfOrigin
Indicates that an entity’s country of origin changed, and this predicate specifies the country that became its origin at a later time than a previously associated country.
-
E.
countryOf
chosen
Indicates that one entity is the country to which another entity belongs, is located in, or is associated with.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.