Triple
T35230594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylab 4 |
E1017222
|
entity |
| Predicate | CSMSerialNumber |
P70012
|
FINISHED |
| Object | CSM-118 |
—
|
NE NERFINISHED |
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: CSM-118 | Statement: [Skylab 4, CSMSerialNumber, CSM-118]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CSMSerialNumber Context triple: [Skylab 4, CSMSerialNumber, CSM-118]
-
A.
LMSerialNumber
Indicates that an entity has or is associated with a specific LM (e.g., "Line Maintenance" or similarly designated) serial number identifier.
-
B.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
C.
capsuleSerialNumber
Indicates that a capsule is associated with a specific identifying serial number.
-
D.
commandModuleSerialNumber
chosen
Indicates that one entity records or specifies the serial number assigned to a command module associated with another entity.
-
E.
builderSerialNumber
Indicates that a builder is associated with a specific serial number that uniquely identifies it.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.