Triple
T24787714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tree of Sobrarbe |
E620162
|
entity |
| Predicate | geographicallyRelatedTo |
P12445
|
FINISHED |
| Object | Pyrenees |
—
|
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: Pyrenees | Statement: [Tree of Sobrarbe, geographicallyRelatedTo, Pyrenees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicallyRelatedTo Context triple: [Tree of Sobrarbe, geographicallyRelatedTo, Pyrenees]
-
A.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
B.
typicalGeographicalAssociation
Indicates a usual or characteristic geographical connection between entities, such as a place commonly associated with a person, group, or phenomenon.
-
C.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
D.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
E.
locationGaveRiseTo
Indicates that a particular location is the origin or source from which something (such as an event, movement, phenomenon, or entity) emerged or developed.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:46 a.m.