Triple
T19471064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teseida |
E487122
|
entity |
| Predicate | containsInvocations |
P104220
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Teseida, containsInvocations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInvocations Context triple: [Teseida, containsInvocations, true]
-
A.
containsInvocation
chosen
Indicates that one entity includes or embeds a call to another operation, function, or method within it.
-
B.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
-
C.
typicalInvocations
Indicates the usual or most common ways in which an action, function, or process is called, used, or carried out.
-
D.
oftenInvokedWith
Indicates that one entity is frequently called, used, or triggered in conjunction with another entity, typically within the same context or operation.
-
E.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e809008190b0021d41b99f9700 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.