Triple
T24786682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | van Keppel |
E620135
|
entity |
| Predicate | hasNotableBranchIn |
P10432
|
FINISHED |
| Object | British nobility |
E89331
|
NE 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: British nobility | Statement: [van Keppel, hasNotableBranchIn, British nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBranchIn Context triple: [van Keppel, hasNotableBranchIn, British nobility]
-
A.
notableBranch
chosen
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
-
B.
presentInBranch
Indicates that something exists or is available within a specific branch or subdivision of a larger organization or structure.
-
C.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
D.
hasControlBranch
Indicates that one entity possesses a controlling or decision-making branch or subdivision within another entity or system.
-
E.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
- F. None of above.
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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a101c25db188190a2c6b998d5d813bd |
completed | May 22, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 4:45 a.m.