Triple
T29859661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya Embedded Language |
E758277
|
entity |
| Predicate | canBeExecutedFrom |
P19950
|
FINISHED |
| Object | Maya Script Editor |
—
|
NE NERFINISHED |
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: Maya Script Editor | Statement: [Maya Embedded Language, canBeExecutedFrom, Maya Script Editor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeExecutedFrom Context triple: [Maya Embedded Language, canBeExecutedFrom, Maya Script Editor]
-
A.
canBeInvokedFrom
chosen
Indicates that one entity (such as a function, method, or component) is able to be called or triggered directly from another specified context or entity.
-
B.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
C.
canBeCalled
Indicates that one entity is able or permitted to be addressed, referred to, or named by another entity in a particular way.
-
D.
canBePerformed
Indicates that a particular action or activity is possible to carry out under given conditions or by a specified agent.
-
E.
isExecutedFor
Indicates that an action, plan, or process is carried out on behalf of, or in service of, a particular entity or purpose.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 29, 2026, 5:48 p.m.