Triple
T9898239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mono |
E182226
|
entity |
| Predicate | runtimeName |
P91052
|
FINISHED |
| Object | Mono runtime |
—
|
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: Mono runtime | Statement: [Mono, runtimeName, Mono runtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimeName Context triple: [Mono, runtimeName, Mono runtime]
-
A.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
B.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
C.
runeName
Indicates that an entity has the specified rune as its name or is identified by that rune name.
-
D.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
E.
launchName
Indicates the designated name or title assigned to a specific launch event or mission.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ac27d88190b8255f7e616f95c9 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:40 p.m.