Triple
T22416745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Brahe |
E554140
|
entity |
| Predicate | memberHeldRank |
P148088
|
FINISHED |
| Object | general |
—
|
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: general | Statement: [House of Brahe, memberHeldRank, general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberHeldRank Context triple: [House of Brahe, memberHeldRank, general]
-
A.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
admitsMemberRank
Indicates that an organization or group accepts individuals holding a specified rank or status as eligible members.
-
C.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
D.
mayHoldRankEquivalentTo
Indicates that one entity is permitted or eligible to possess a rank that is considered equivalent in status or level to the rank held by another entity.
-
E.
hasEnlistedRank
Indicates that an individual holds an enlisted (non-officer) rank within a military or similar hierarchical organization.
- F. None of above. chosen
Provenance (4 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15946cd2c8190bdec0348de6ebcb9 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.