Triple
T34543529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapnik |
E886864
|
entity |
| Predicate | hasBindingsIn |
P181800
|
FINISHED |
| Object | Python |
—
|
NE NERFINISHED |
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: Python | Statement: [Mapnik, hasBindingsIn, Python]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBindingsIn Context triple: [Mapnik, hasBindingsIn, Python]
-
A.
isBindingIn
Indicates that one entity functions as a binding site or context in which another entity is bound or attached.
-
B.
hasBindingForce
Indicates that one entity (such as a rule, agreement, or decision) is legally or normatively obligatory and must be followed or enforced by another entity.
-
C.
hasExpressionIn
Indicates that one entity is manifested, represented, or realized within another entity, typically as a specific form, version, or expression.
-
D.
bindsTo
Indicates that one entity physically or functionally attaches or connects to another, often with some specificity or selectivity in the interaction.
-
E.
isInitiallyBoundWith
Indicates that two or more entities are connected, associated, or constrained together at the starting point of a process, state, or interaction.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 2:02 a.m.