Triple
T37016709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tale of the Cat |
E916100
|
entity |
| Predicate | notableProgenyRegion |
P205696
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [Tale of the Cat, notableProgenyRegion, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProgenyRegion Context triple: [Tale of the Cat, notableProgenyRegion, North America]
-
A.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
B.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
C.
allegedBirthRegion
Indicates the region where an entity is claimed or reported to have been born, without asserting that this birthplace is verified as fact.
-
D.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
notableChildren
Indicates that the subject has children who are notable or significant in some recognized way.
- F. None of above. chosen
Provenance (5 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c317ce081909e593f3a8cb51cc8 |
completed | June 26, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.