Triple
T29396936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBE used for male honorary knights |
E745524
|
entity |
| Predicate | indicatesHonoraryStatus |
P40137
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [KBE used for male honorary knights, indicatesHonoraryStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesHonoraryStatus Context triple: [KBE used for male honorary knights, indicatesHonoraryStatus, true]
-
A.
hasHonoraryMember
Indicates that an entity is recognized as an honorary (non-regular) member of another entity, typically without full rights or obligations of standard membership.
-
B.
hasHonorificStatus
chosen
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
C.
confersHonorificStatus
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
-
D.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
E.
honoraryAwardsEligibleFor
Indicates that an entity qualifies to receive one or more honorary awards.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:47 p.m.