Triple
T23286500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehetia |
E589000
|
entity |
| Predicate | hasLimitedLandingSites |
P151709
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mehetia, hasLimitedLandingSites, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedLandingSites Context triple: [Mehetia, hasLimitedLandingSites, true]
-
A.
hasMainLandingSite
Indicates that an entity has a primary or principal location where it arrives, lands, or makes contact.
-
B.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
C.
hasLandings
Indicates that an entity has one or more associated landing events or landing locations.
-
D.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
E.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
- F. None of above. chosen
Provenance (4 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19647178c8190bbca5da38472ce05 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 5 p.m.