Triple
T27384857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-65 |
E691338
|
entity |
| Predicate | acronymOfPrimaryPayload |
P89379
|
FINISHED |
| Object | IML-2 |
E476110
|
NE 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: IML-2 | Statement: [STS-65, acronymOfPrimaryPayload, IML-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acronymOfPrimaryPayload Context triple: [STS-65, acronymOfPrimaryPayload, IML-2]
-
A.
primaryPayloadAcronym
chosen
Indicates that an entity’s primary payload is identified or referred to by a specific acronym.
-
B.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
-
C.
acronymOfCorePlan
Indicates that one entity is the acronym or abbreviated form of the core plan represented by the other entity.
-
D.
abbreviationOfPrimaryCustomer
Indicates that one entity is an abbreviation or shortened form of the name or identifier of the primary customer entity.
-
E.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
- F. None of above.
Provenance (4 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c89b7b88190a8b2af842f5f9cca |
completed | May 2, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12a7ede8688190aaad6460b5bad00f |
completed | May 24, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:24 p.m.