Triple
T17312525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alto Executive |
E420333
|
entity |
| Predicate | primaryOutputMethod |
P1302
|
FINISHED |
| Object | text display |
—
|
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: text display | Statement: [Alto Executive, primaryOutputMethod, text display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOutputMethod Context triple: [Alto Executive, primaryOutputMethod, text display]
-
A.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
B.
primaryMode
chosen
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
C.
languageOfPrimaryOutput
Indicates the language in which the primary output or main result of an entity (such as a work, process, or system) is expressed.
-
D.
standardOutput
Indicates that one entity produces data or results that are directed to another entity’s standard output stream.
-
E.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399a4194819091d34cd3fffc8072 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.