Triple

T11958677
Position Surface form Disambiguated ID Type / Status
Subject GNATmake E284614 entity
Predicate invocationExample P8562 FINISHED
Object gnatmake main.adb 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: gnatmake main.adb | Statement: [GNATmake, invocationExample, gnatmake main.adb]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: invocationExample
Context triple: [GNATmake, invocationExample, gnatmake main.adb]
  • A. 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.
  • B. invocationType
    Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
  • C. toolUseExamples chosen
    Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
  • D. invokesPower
    Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
  • E. openingInvocation
    Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
  • 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903681a00819098c2b5260e2ef834 completed April 10, 2026, 2:04 p.m.
PD Predicate disambiguation batch_69d8bb3e48e08190b2fee43af4f57323 completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:45 p.m.