Triple
T32325483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muglins Lighthouse |
E825899
|
entity |
| Predicate | mannedStatus |
P53984
|
FINISHED |
| Object | unmanned |
—
|
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: unmanned | Statement: [Muglins Lighthouse, mannedStatus, unmanned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mannedStatus Context triple: [Muglins Lighthouse, mannedStatus, unmanned]
-
A.
crewed
Indicates that an entity is operated, staffed, or manned by one or more people who serve as its crew.
-
B.
mannedFlightOutcome
Indicates the result or status of a crewed (manned) spaceflight mission, such as success, failure, or partial success.
-
C.
isPermanentlyCrewed
Indicates that an object, such as a facility or vehicle, consistently has a crew present on a continuous, ongoing basis without planned periods of being uncrewed.
-
D.
astronautStatus
Indicates the role or condition of an entity specifically in relation to being an astronaut (e.g., active, retired, candidate).
-
E.
isUncrewed
chosen
Indicates that an object, vehicle, or mission operates without any human crew physically on board.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde7cd8481908d3128d089c86c14 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:47 a.m.