Triple
T23336368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capet |
E591596
|
entity |
| Predicate | broaderTerm |
P57966
|
FINISHED |
| Object | European royal dynastic surnames |
—
|
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: European royal dynastic surnames | Statement: [Capet, broaderTerm, European royal dynastic surnames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broaderTerm Context triple: [Capet, broaderTerm, European royal dynastic surnames]
-
A.
generalizationOf
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
-
B.
generalizationTo
chosen
Indicates that one concept or entity is a more general, abstract, or encompassing version of another, capturing a broader category or superset relationship.
-
C.
broaderProcess
Indicates that one process encompasses, includes, or provides the larger context for another, more specific process.
-
D.
isBroad
Indicates that something has a large width or extensive scope relative to a reference or context.
-
E.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f1e0588190bf073b92be0bf9e4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:16 p.m.