Triple
T3974592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lalande-de-Pomerol |
E85608
|
entity |
| Predicate | comparisonToNeighbor |
P278
|
FINISHED |
| Object | more approachable than Pomerol |
—
|
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: more approachable than Pomerol | Statement: [Lalande-de-Pomerol, comparisonToNeighbor, more approachable than Pomerol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparisonToNeighbor Context triple: [Lalande-de-Pomerol, comparisonToNeighbor, more approachable than Pomerol]
-
A.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
B.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
-
C.
comparisonSet
Indicates that one entity is part of a group of entities that are being compared or evaluated against each other.
-
D.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
E.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.