Triple
T36641930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buildroot |
E904606
|
entity |
| Predicate | supportsCStandardLibrary |
P203
|
FINISHED |
| Object | glibc |
E61955
|
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: glibc | Statement: [Buildroot, supportsCStandardLibrary, glibc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCStandardLibrary Context triple: [Buildroot, supportsCStandardLibrary, glibc]
-
A.
standardLibraryVersion
Indicates the specific version of a standard library that is associated with or used by an entity.
-
B.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
-
D.
includesStandard
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
-
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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a097475e081908086bd1b477456f3 |
completed | June 23, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.