Triple
T25750408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis |
E648455
|
entity |
| Predicate | sampleConditionAfterLanding |
P55418
|
FINISHED |
| Object | collector arrays broken |
—
|
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: collector arrays broken | Statement: [Genesis, sampleConditionAfterLanding, collector arrays broken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleConditionAfterLanding Context triple: [Genesis, sampleConditionAfterLanding, collector arrays broken]
-
A.
hasLandingConditions
chosen
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
B.
communicationAfterLanding
Indicates that a communication event occurs after a landing has taken place.
-
C.
crewLandingStatus
Indicates the status or outcome of a crew’s landing event, such as whether and how the crew has successfully landed.
-
D.
landingAfterAction
Indicates that one entity performs a landing event that occurs after a specified preceding action has taken place.
-
E.
landingRecovery
Indicates the process or method by which something is retrieved or secured after it has landed.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 4:34 a.m.