Triple
T15846054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tama-nui-te-rā |
E384215
|
entity |
| Predicate | movesAcross |
P30219
|
FINISHED |
| Object | the sky |
—
|
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: the sky | Statement: [Tama-nui-te-rā, movesAcross, the sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movesAcross Context triple: [Tama-nui-te-rā, movesAcross, the sky]
-
A.
movementAcross
chosen
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
-
B.
movesFrom
Indicates that an entity changes location by departing or originating from a specified place.
-
C.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
D.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
E.
across
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14ca636048190bc89cd8b4efa89e9 |
completed | April 16, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.