Triple
T20073467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table of Seven (Septemvirate) |
E499795
|
entity |
| Predicate | selectionBasisForMembers |
P136
|
FINISHED |
| Object | noble status |
—
|
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: noble status | Statement: [Table of Seven (Septemvirate), selectionBasisForMembers, noble status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionBasisForMembers Context triple: [Table of Seven (Septemvirate), selectionBasisForMembers, noble status]
-
A.
selectsMembersBy
Indicates that an entity chooses or designates specific members from a larger group or collection based on some criteria.
-
B.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
C.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
E.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66439efe881909a068c3f05022421 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.