Triple
T10456442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | libSystem |
E246562
|
entity |
| Predicate | dependencyOf |
P1022
|
FINISHED |
| Object | Foundation framework |
—
|
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: Foundation framework | Statement: [libSystem, dependencyOf, Foundation framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dependencyOf Context triple: [libSystem, dependencyOf, Foundation framework]
-
A.
dependency
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
-
B.
crownDependencyOf
Indicates that one entity is a Crown dependency that is self-governing but under the sovereignty or jurisdiction of another entity (typically a state or monarch).
-
C.
hasDependency
chosen
Indicates that one entity relies on or requires another entity in order to function, exist, or be fulfilled.
-
D.
conceptuallyDependsOn
Indicates that one entity’s definition, validity, or understanding relies on or is grounded in the concepts provided by another entity.
-
E.
representationDependsOn
Indicates that one representation is reliant on or derived from another representation in order to be valid, complete, or interpretable.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe498a808190b88530f0221df4a6 |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.