Triple
T33506541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arvingerne |
E858126
|
entity |
| Predicate | featuresCharacterFamilyName |
P98396
|
FINISHED |
| Object | Grønnegaard |
—
|
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: Grønnegaard | Statement: [Arvingerne, featuresCharacterFamilyName, Grønnegaard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterFamilyName Context triple: [Arvingerne, featuresCharacterFamilyName, Grønnegaard]
-
A.
featuresFamilyName
chosen
Indicates that an entity is associated with or displays a particular family name.
-
B.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
C.
featuresFamily
Indicates that something includes, presents, or highlights a family as a central element or subject.
-
D.
nameFamily
Indicates that one entity is the family name (surname) of another entity.
-
E.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
Created at: May 1, 2026, 1:38 a.m.