Triple
T25703958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laputa |
E644536
|
entity |
| Predicate | locationRelativeToEarth |
P81574
|
FINISHED |
| Object | floating above Balnibarbi |
—
|
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: floating above Balnibarbi | Statement: [Laputa, locationRelativeToEarth, floating above Balnibarbi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToEarth Context triple: [Laputa, locationRelativeToEarth, floating above Balnibarbi]
-
A.
positionRelativeToEarth
chosen
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
B.
motionRelativeToEarth
Indicates movement or change in position of an entity as measured or perceived relative to the Earth as a reference frame.
-
C.
locationRelativeToPitch
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
-
D.
locationRelativeToIP
Indicates a spatial or geographic relationship between an entity and a given IP address’s inferred location.
-
E.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 21, 2026, 9 p.m.