Triple
T34614739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Python 3.7 |
E888830
|
entity |
| Predicate | hasBuiltInFunction |
P56539
|
FINISHED |
| Object | breakpoint |
—
|
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: breakpoint | Statement: [Python 3.7, hasBuiltInFunction, breakpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltInFunction Context triple: [Python 3.7, hasBuiltInFunction, breakpoint]
-
A.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
B.
hasFunctionInLegends
Indicates that an entity serves a particular role, purpose, or activity within legendary stories, myths, or folklore.
-
C.
containsFunction
chosen
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
D.
hasCoreFunction
Indicates that one entity serves as a primary or essential function or role of another entity.
-
E.
hasUserFunction
Indicates that an entity is associated with, or assigned, a particular user-related role, capability, or function.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.