Triple
T29749402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Army regiments |
E752851
|
entity |
| Predicate | followDoctrine |
P27401
|
FINISHED |
| Object | French Army doctrine |
—
|
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: French Army doctrine | Statement: [French Army regiments, followDoctrine, French Army doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followDoctrine Context triple: [French Army regiments, followDoctrine, French Army doctrine]
-
A.
followsDoctrine
chosen
Indicates that one entity adheres to, complies with, or acts in accordance with a specified doctrine or set of guiding principles.
-
B.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
C.
alternativeDoctrine
Indicates that one doctrine serves as an alternative or substitute to another doctrine within a given context.
-
D.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
E.
currentDoctrine
Indicates the doctrine, policy, or set of guiding principles that is presently in force or officially adopted at a given 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 7:53 p.m.