Triple
T4191960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Tower and Sword |
E89056
|
entity |
| Predicate | highestOrderOf |
P14338
|
FINISHED |
| Object | Portuguese honors system |
—
|
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: Portuguese honors system | Statement: [Order of the Tower and Sword, highestOrderOf, Portuguese honors system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestOrderOf Context triple: [Order of the Tower and Sword, highestOrderOf, Portuguese honors system]
-
A.
highestElement
Indicates that one element in a set or collection has a value greater than or equal to all other elements according to a specified ordering.
-
B.
mostSignificantBit
Indicates that one value represents the most significant (highest-order) bit in the binary representation of another value.
-
C.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
D.
highestPart
Indicates that one entity is the topmost or uppermost portion of another entity.
-
E.
highestOrgan
chosen
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.