Triple
T33901283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 Command and Service Module |
E869052
|
entity |
| Predicate | carriedCommunicationsSystem |
P84312
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Apollo 15 Command and Service Module, carriedCommunicationsSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedCommunicationsSystem Context triple: [Apollo 15 Command and Service Module, carriedCommunicationsSystem, yes]
-
A.
hasCommunicationSystems
chosen
Indicates that one entity is equipped with or possesses communication systems used for transmitting or receiving information.
-
B.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
C.
carriesCrewOf
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
-
D.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
crewCab
Indicates that a vehicle has a crew cab configuration, meaning its cabin is designed to seat multiple occupants in both front and rear rows.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:48 a.m.