Triple
T13692756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMM1 |
E328308
|
entity |
| Predicate | hasCompanionIndex |
P111193
|
FINISHED |
| Object | RMM2 |
—
|
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: RMM2 | Statement: [RMM1, hasCompanionIndex, RMM2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionIndex Context triple: [RMM1, hasCompanionIndex, RMM2]
-
A.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
-
B.
hasCompanionCore
Indicates that an entity is associated with, or accompanied by, a specific companion core.
-
C.
hasCompanionRoute
Indicates that one route is associated with another route that serves as its companion, typically running in parallel, in the opposite direction, or as a complementary service.
-
D.
hasCompanionMagnitude
Indicates that one entity is associated with another entity whose magnitude (such as size, intensity, or value) is being specified or characterized.
-
E.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
- F. None of above. chosen
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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.