Triple
T33329752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese heraldry |
E853369
|
entity |
| Predicate | usesOrdinary |
P176501
|
FINISHED |
| Object | cross |
—
|
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: cross | Statement: [Portuguese heraldry, usesOrdinary, cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOrdinary Context triple: [Portuguese heraldry, usesOrdinary, cross]
-
A.
currentOrdinary
Indicates that an entity currently holds or is in the state of an ordinary (non-special or non-exceptional) status or role.
-
B.
ordinary
Indicates that something or someone is typical, usual, or not special or exceptional in the relevant context.
-
C.
ordinaryMayBe
Indicates that something is typically or commonly allowed, possible, or permitted under normal circumstances.
-
D.
firstOrdinary
Indicates that the subject is the first entity to hold or occupy an ordinary (non-special, standard) position, role, or status in a given sequence or context.
-
E.
ordinaryType
Indicates that something belongs to a standard, non-specialized, or default category or type within a given classification.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:34 a.m.