Triple
T4132952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Lorraine |
E85082
|
entity |
| Predicate | ordinary |
P54041
|
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: [coat of arms of Lorraine, ordinary, bend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinary Context triple: [coat of arms of Lorraine, ordinary, bend]
-
A.
pastOrdinary
Indicates that the related action or state occurred in the past using the simple (non-progressive, non-perfect) tense.
-
B.
currentOrdinary
Indicates that an entity currently holds or is in the state of an ordinary (non-special or non-exceptional) status or role.
-
C.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
D.
export
Indicates that one entity sends goods, services, or data out from its own domain or territory to another entity or external destination.
-
E.
typicallySpared
Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
- 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_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_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:42 p.m.