Triple
T20990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Merit |
E416
|
entity |
| Predicate | additionalMembersType |
P121
|
FINISHED |
| Object | honorary 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: honorary members | Statement: [Order of Merit, additionalMembersType, honorary members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalMembersType Context triple: [Order of Merit, additionalMembersType, honorary members]
-
A.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
B.
foundingMember
Indicates that an entity is one of the original creators or initial participants involved in establishing another entity, such as an organization, group, or project.
-
C.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
D.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
E.
formerMemberOf
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246f7bd30819085f751c41f6f029e |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a246526f5881909bc2a46e978bd082 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.