Triple
T19845917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European–Asian boundary region |
E476858
|
entity |
| Predicate | definitionVariesBy |
P36743
|
FINISHED |
| Object | country |
—
|
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: country | Statement: [European–Asian boundary region, definitionVariesBy, country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definitionVariesBy Context triple: [European–Asian boundary region, definitionVariesBy, country]
-
A.
termVariesBy
chosen
Indicates that the value or meaning of a term changes depending on a specified factor, such as context, dimension, or condition.
-
B.
structureVariesBy
Indicates that the structure or configuration of one entity changes depending on or is different for another specified factor or context.
-
C.
attributeVariesBy
Indicates that a particular attribute can take on different values depending on another variable, context, or condition.
-
D.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
E.
compositionVariesBy
Indicates that the composition of something differs depending on a specified factor, condition, or 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658091c608190b4eb9bcedd88e147 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.