Triple
T4136959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Red |
E85176
|
entity |
| Predicate | countryOnD-Day |
P878
|
FINISHED |
| Object | German-occupied France |
—
|
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: German-occupied France | Statement: [Queen Red, countryOnD-Day, German-occupied France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOnD-Day Context triple: [Queen Red, countryOnD-Day, German-occupied France]
-
A.
countryOnAlliedSide
Indicates that a country is aligned with and actively supports a particular side or coalition in a conflict, alliance, or broader geopolitical context.
-
B.
country1
Indicates that the subject entity is a country (or represents a country) in the given context.
-
C.
countryDuring
Indicates that one entity exists, occurs, or is valid within the temporal span during which the other entity is recognized as a specific country.
-
D.
alliedCountries
Indicates that two countries are formally cooperating as allies, typically through mutual support agreements or shared strategic interests.
-
E.
countryAtTheTime
chosen
Indicates that an entity is associated with a specific country as it existed at a particular point in time.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.