Triple
T22274953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Montesa |
E550576
|
entity |
| Predicate | crossForm |
P147659
|
FINISHED |
| Object | red Greek cross with fleur-de-lis ends |
—
|
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: red Greek cross with fleur-de-lis ends | Statement: [Order of Montesa, crossForm, red Greek cross with fleur-de-lis ends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossForm Context triple: [Order of Montesa, crossForm, red Greek cross with fleur-de-lis ends]
-
A.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
B.
crossWith
Indicates that one entity intersects or passes over/through the path, boundary, or position of another entity.
-
C.
crossCut
Indicates that one entity intersects or passes through another, typically cutting across it from one side to the other.
-
D.
crossStructure
Indicates that one entity passes over, through, or across the physical span or boundary defined by another structure.
-
E.
crossErectedBy
Indicates that a particular cross was constructed, installed, or set up by a specified agent or entity.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea643d48190985371d01aac7bfc |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.