Triple
T19394044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent Multipurpose Module |
E485140
|
entity |
| Predicate | permanentlyAttached |
P10139
|
FINISHED |
| Object | 2011-03-01 |
—
|
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: 2011-03-01 | Statement: [Permanent Multipurpose Module, permanentlyAttached, 2011-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentlyAttached Context triple: [Permanent Multipurpose Module, permanentlyAttached, 2011-03-01]
-
A.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
madePermanentBy
Indicates that one entity causes another entity, condition, or status to become lasting, fixed, or indefinitely maintained.
-
C.
permanentPosition
Indicates that an entity holds a long-term, ongoing role or job with another entity, without a predefined end date.
-
D.
permanentAdoption
Indicates a lasting, legally recognized adoption relationship in which the adoptee becomes a permanent member of the adopter’s family.
-
E.
isPermanentBody
Indicates that an entity functions as an enduring, officially established body or organization that is not temporary or ad hoc.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b47630881909ba390888b8779f6 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.