Triple
T8118148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCP |
E189531
|
entity |
| Predicate | executesFrom |
P52277
|
FINISHED |
| Object | RAM |
—
|
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: RAM | Statement: [CCP, executesFrom, RAM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executesFrom Context triple: [CCP, executesFrom, RAM]
-
A.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
B.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
C.
launchesFrom
chosen
Indicates that an object or agent initiates its movement, operation, or departure starting at a specified location or source.
-
D.
executedAlongWith
Indicates that one entity was carried out, performed, or implemented in conjunction with another entity, at the same time or as part of the same operation or event.
-
E.
executionBy
Indicates that one entity carries out or performs the execution (killing or implementation of a death sentence) of another entity.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.