Triple
T29407425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PyGObject |
E745806
|
entity |
| Predicate | supportsIntrospectionFor |
P86661
|
FINISHED |
| Object | GTK |
E203866
|
NE 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: GTK | Statement: [PyGObject, supportsIntrospectionFor, GTK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntrospectionFor Context triple: [PyGObject, supportsIntrospectionFor, GTK]
-
A.
supportsIntrospectionOf
chosen
Indicates that one entity enables or facilitates the examination or analysis of the internal state, structure, or behavior of another entity.
-
B.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving another entity.
-
C.
isIntendedToSupport
Indicates that one entity is designed or purposed to provide assistance, reinforcement, or backing to another entity or activity.
-
D.
isSupportedFor
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
-
E.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
- F. None of above.
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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870c4762c81908a9fdcb04f0188d3 |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 2:55 p.m.