Triple
T23372048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Раикоке |
E593500
|
entity |
| Predicate | расположенМежду |
P1262
|
FINISHED |
| Object | остров Матуа |
—
|
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: остров Матуа | Statement: [Раикоке, расположенМежду, остров Матуа]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: расположенМежду Context triple: [Раикоке, расположенМежду, остров Матуа]
-
A.
locatedBetween
chosen
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
takesPlaceBetween
Indicates that an event or interaction occurs within the temporal or spatial interval defined by two reference points.
-
C.
livesBetween
Indicates that one entity resides at a location that is spatially situated between two other reference entities or locations.
-
D.
metBetween
Indicates that two or more entities had an in-person or virtual meeting or encounter with each other during a specified time or context.
-
E.
formedBetween
Indicates a relationship in which a connection, bond, or structure has come into existence linking two or more entities.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.