Triple
T18722484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Companion of Honour |
E457810
|
entity |
| Predicate | limitOnMembers |
P21198
|
FINISHED |
| Object | restricted number of members |
—
|
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: restricted number of members | Statement: [Companion of Honour, limitOnMembers, restricted number of members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitOnMembers Context triple: [Companion of Honour, limitOnMembers, restricted number of members]
-
A.
limitedNumberOfMembers
Indicates that the associated group or entity has a maximum allowed number of members or participants.
-
B.
limitedMembershipTo
Indicates that access, participation, or inclusion in something is restricted to a specific subset of entities or members.
-
C.
hasMaximumNumberOfMembers
chosen
Indicates that there is an upper limit on how many members can be associated with a given entity.
-
D.
additionalMembersAllowed
Indicates that more members are permitted to be added beyond those already included or initially specified.
-
E.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56abc1c708190917f6bfea0548c42 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.