Triple
T37779497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Argentines |
E941787
|
entity |
| Predicate | subregionOfAncestralOrigin |
P58741
|
FINISHED |
| Object | Central Europe |
—
|
NE NERFINISHED |
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: Central Europe | Statement: [Austrian Argentines, subregionOfAncestralOrigin, Central Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subregionOfAncestralOrigin Context triple: [Austrian Argentines, subregionOfAncestralOrigin, Central Europe]
-
A.
ancestralSubgroups
Indicates that one group consists of or descends from earlier, foundational subgroups within a lineage or hierarchy.
-
B.
secondaryAncestralHomeland
Indicates a place that serves as an additional or subsequent ancestral homeland for a group or lineage, distinct from their primary place of origin.
-
C.
originSubregion
chosen
Indicates the specific subregional area from which an entity originates or is derived.
-
D.
proposedAsAncestralOriginOf
Indicates that something is suggested or hypothesized to be the ancestral source or origin of something else.
-
E.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf48082c8190bf83c4c2c9733c2b |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.