Triple
T33719580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | double cross of Lorraine |
E863973
|
entity |
| Predicate | hasUpperBar |
P81815
|
FINISHED |
| Object | shorter horizontal bar |
—
|
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: shorter horizontal bar | Statement: [double cross of Lorraine, hasUpperBar, shorter horizontal bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperBar Context triple: [double cross of Lorraine, hasUpperBar, shorter horizontal bar]
-
A.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
-
B.
hasBars
chosen
Indicates that one entity possesses, contains, or is equipped with bars as a defining feature or component.
-
C.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
D.
hasBarStrength
Indicates that one entity possesses or exhibits a certain level or measure of bar-related strength or robustness in relation to another entity or context.
-
E.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.