Triple
T18654709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the House of Dreux |
E456028
|
entity |
| Predicate | ordinaryType |
P132163
|
FINISHED |
| Object | bend |
—
|
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: bend | Statement: [Arms of the House of Dreux, ordinaryType, bend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinaryType Context triple: [Arms of the House of Dreux, ordinaryType, bend]
-
A.
ordinary
Indicates that something or someone is typical, usual, or not special or exceptional in the relevant context.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
ordinaryMayBe
Indicates that something is typically or commonly allowed, possible, or permitted under normal circumstances.
-
D.
ordinaryPosition
Indicates that an entity occupies its usual or standard position relative to a reference frame or context.
-
E.
currentOrdinary
Indicates that an entity currently holds or is in the state of an ordinary (non-special or non-exceptional) status or role.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55084012881909b9dd60565011c86 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.