Triple
T28609403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FormatGuard |
E724134
|
entity |
| Predicate | wrapsFunctionFamily |
P164912
|
FINISHED |
| Object | printf |
—
|
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: printf | Statement: [FormatGuard, wrapsFunctionFamily, printf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrapsFunctionFamily Context triple: [FormatGuard, wrapsFunctionFamily, printf]
-
A.
linkFunctionFamily
Indicates a relationship where one function is associated with or belongs to a particular family of related functions.
-
B.
packagingFunction
Indicates that one entity serves a packaging-related role or function in relation to another entity (e.g., how something is packed, contained, or presented).
-
C.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
-
D.
transfersFunctionFrom
Indicates that a function, role, or operational capability is moved or reassigned from one entity to another.
-
E.
PLEXFunction
Indicates a functional or operational role that one entity performs or serves for another within a system or context.
- F. None of above. chosen
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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:29 a.m.