Triple
T38477126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classified |
E915577
|
entity |
| Predicate | mapSetting |
P190940
|
FINISHED |
| Object | Pentagon |
—
|
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: Pentagon | Statement: [Classified, mapSetting, Pentagon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapSetting Context triple: [Classified, mapSetting, Pentagon]
-
A.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
B.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
-
C.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
-
D.
mapSource
Indicates the original data, document, or resource from which a map or mapping representation is derived.
-
E.
mapTheme
Indicates a thematic relationship where a map is associated with, organized by, or visually represents a particular theme or subject.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.