Triple
T29404595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GObject |
E745748
|
entity |
| Predicate | supportsIntrospection |
P203
|
FINISHED |
| Object | GObject Introspection |
E745801
|
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: GObject Introspection | Statement: [GObject, supportsIntrospection, GObject Introspection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntrospection Context triple: [GObject, supportsIntrospection, GObject Introspection]
-
A.
supportsIntrospectionOf
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.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
-
E.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_6a035ead9ee0819099806d2670dc9c50 |
completed | May 12, 2026, 5:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25d91aa7cc819082409393cd289019 |
completed | June 7, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_6a035dc9210c8190a9044c6a53211520 |
completed | May 12, 2026, 5:05 p.m. |
Created at: April 28, 2026, 2:53 p.m.