Triple
T18051249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heapq |
E431929
|
entity |
| Predicate | heappushSignature |
P129630
|
FINISHED |
| Object | heappush(heap, item) |
—
|
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: heappush(heap, item) | Statement: [heapq, heappushSignature, heappush(heap, item)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heappushSignature Context triple: [heapq, heappushSignature, heappush(heap, item)]
-
A.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
B.
signatureEventOf
Indicates that a given event represents or records the signing (or creation) of the associated entity, such as a document, agreement, or artifact.
-
C.
hasSignatureMechanic
Indicates that an entity (such as a game, character, or system) possesses a distinctive, defining mechanic or feature that is uniquely characteristic of it.
-
D.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
E.
usesSignatureMove
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c0fe4f1881908fa8485cb3ccfa44 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.