Triple
T34208173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian wolf |
E877572
|
entity |
| Predicate | recolonization |
P43601
|
FINISHED |
| Object | Western Alps |
—
|
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: Western Alps | Statement: [Italian wolf, recolonization, Western Alps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recolonization Context triple: [Italian wolf, recolonization, Western Alps]
-
A.
colonizes
Indicates that one entity establishes control or settlement over another entity’s territory or domain, often imposing its presence, systems, or influence there.
-
B.
colonizationPattern
Indicates the characteristic way in which one entity establishes, spreads, and organizes its presence or control over another entity or area.
-
C.
colonized
Indicates that one entity established control over and settled in the territory of another entity, often imposing its own systems, structures, or population there.
-
D.
colonizationDirection
Indicates the directional relationship from a colonizing entity toward the target or region being colonized.
-
E.
repopulatedBy
chosen
Indicates that something is populated again or refilled with members or inhabitants by a specified agent or source.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71052707c8190b6b514bf87a4bc79 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.