Triple
T9852584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouvrage Hackenberg |
E239503
|
entity |
| Predicate | designedBy |
P184
|
FINISHED |
| Object | CORF |
E272674
|
NE 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: CORF | Statement: [Ouvrage Hackenberg, designedBy, CORF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CORF Context triple: [Ouvrage Hackenberg, designedBy, CORF]
-
A.
CORF
chosen
CORF is the French military commission responsible for planning and overseeing the construction of fortified regions, notably including major works of the Maginot Line.
-
B.
CoR
CoR is the commonly used abbreviation for the European Committee of the Regions, the EU’s advisory body representing local and regional authorities.
-
C.
COUR
COUR is the stock ticker symbol for Coursera, a major online learning platform offering courses, certificates, and degrees from universities and companies worldwide.
-
D.
CJO
CJO is the abbreviated title for the senior military officer responsible for overseeing joint operations across multiple service branches.
-
E.
CRF
CRF is a military acronym most notably used for Japan’s former Central Readiness Force, a rapid-deployment command within the Japan Ground Self-Defense Force.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb375ba448190a32cca2b0f376ac1 |
completed | April 2, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d5ee190c8190957451d8d8291df3 |
completed | April 5, 2026, 3:24 a.m. |
Created at: March 30, 2026, 8:34 p.m.