Triple
T34415956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negation |
E883403
|
entity |
| Predicate | mapsFalseTo |
P178919
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Negation, mapsFalseTo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapsFalseTo Context triple: [Negation, mapsFalseTo, true]
-
A.
mapsTo
Indicates that one entity is associated with or transformed into another entity, typically defining a directional correspondence or function from a source to a target.
-
B.
mappingBy
Indicates that one entity is related to another through a defined mapping or association, specifying which side or field governs the relationship.
-
C.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
D.
canMap
Indicates that one entity is able to be mapped or transformed systematically into another entity or representation.
-
E.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 1:59 a.m.