Triple
T13699601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The High Table |
E328481
|
entity |
| Predicate | hasMottoLikePrinciple |
P33142
|
FINISHED |
| Object | rules and consequences |
—
|
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: rules and consequences | Statement: [The High Table, hasMottoLikePrinciple, rules and consequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoLikePrinciple Context triple: [The High Table, hasMottoLikePrinciple, rules and consequences]
-
A.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
B.
hasMottoLikeFunction
chosen
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
C.
hasMottoAuthority
Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for another entity.
-
D.
hasMottoTradition
Indicates that an entity possesses a traditional motto associated with its identity or heritage.
-
E.
mottoEmphasizes
Indicates that a motto highlights, stresses, or gives special importance to a particular idea, value, or theme.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.