Triple
T7340672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France Modern |
E169237
|
entity |
| Predicate | inspiredLaterArms |
P77207
|
FINISHED |
| Object | royal arms of Bourbon monarchies in Europe |
—
|
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: royal arms of Bourbon monarchies in Europe | Statement: [France Modern, inspiredLaterArms, royal arms of Bourbon monarchies in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredLaterArms Context triple: [France Modern, inspiredLaterArms, royal arms of Bourbon monarchies in Europe]
-
A.
laterArm
Indicates that one event, state, or action occurs at a later time than another within the same arm or branch of a process or study.
-
B.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
C.
greaterArmsFeature
Indicates that one entity possesses a more prominent or advanced arm-related feature than another entity.
-
D.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
E.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f3463d0481908aed9ed43a8ac6a8 |
completed | March 27, 2026, 9:14 p.m. |
Created at: March 27, 2026, 3:04 p.m.