Triple
T15740071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leontice |
E381577
|
entity |
| Predicate | isTraditionallyPlacedIn |
P13132
|
FINISHED |
| Object | barberry family |
—
|
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: barberry family | Statement: [Leontice, isTraditionallyPlacedIn, barberry family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionallyPlacedIn Context triple: [Leontice, isTraditionallyPlacedIn, barberry family]
-
A.
isTraditionallyOccupiedBy
Indicates that a place, territory, or role has historically and customarily been inhabited or held by a particular group or type of entity.
-
B.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
C.
traditionallyResidesIn
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
-
D.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
E.
traditionallyFoundIn
chosen
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.