Triple
T11958952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gperftools |
E284620
|
entity |
| Predicate | profilingOutputFormat |
P76298
|
FINISHED |
| Object | call-graph data |
—
|
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: call-graph data | Statement: [gperftools, profilingOutputFormat, call-graph data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: profilingOutputFormat Context triple: [gperftools, profilingOutputFormat, call-graph data]
-
A.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
B.
outputConfiguration
chosen
Indicates how the results or data produced by a process, system, or component are structured, formatted, or directed to their destination.
-
C.
outputProperty
Indicates that a property or attribute is produced, exposed, or yielded as the output of a process, function, or system.
-
D.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
E.
selectionFormat
Indicates the specific structure or style in which a selection or choice is represented or presented.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.