Triple
T28111001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandin and Yambo twin lakes |
E710486
|
entity |
| Predicate | pairRelationship |
P10690
|
FINISHED |
| Object | side-by-side lakes |
—
|
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: side-by-side lakes | Statement: [Pandin and Yambo twin lakes, pairRelationship, side-by-side lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairRelationship Context triple: [Pandin and Yambo twin lakes, pairRelationship, side-by-side lakes]
-
A.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
B.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
C.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
E.
trackRelationship
Indicates a connection in which one entity monitors, follows, or keeps a record of another entity’s state, behavior, or changes over time.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640c75684819090935f5fb0716c29 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:11 p.m.