Triple
T14653673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Lovers and a Bear |
E344053
|
entity |
| Predicate | hasPolarSetting |
P115219
|
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: [Two Lovers and a Bear, hasPolarSetting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolarSetting Context triple: [Two Lovers and a Bear, hasPolarSetting, true]
-
A.
hasPolarCoverage
Indicates that an entity includes or provides coverage, presence, or applicability in polar regions.
-
B.
hasPolarRadius
Indicates that an entity possesses a specific radius measured from its center to its pole, typically used for spheroidal or planetary bodies.
-
C.
hasPolarEquation
Indicates that an entity is associated with, or can be represented by, a specific equation expressed in polar coordinates.
-
D.
hasPoleAt
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
-
E.
hasEccentricSetting
Indicates that something is characterized by an unusual, unconventional, or quirky setting or environment.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb518f7dc8190877997ea4cd3eed2 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:27 a.m.