Triple
T28346705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atsumi Peninsula |
E717973
|
entity |
| Predicate | hasNotableCape |
P54847
|
FINISHED |
| Object | Cape Irago |
—
|
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: Cape Irago | Statement: [Atsumi Peninsula, hasNotableCape, Cape Irago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCape Context triple: [Atsumi Peninsula, hasNotableCape, Cape Irago]
-
A.
hasCape
Indicates that one entity possesses or is wearing a cape.
-
B.
containsCape
chosen
Indicates that one entity includes or has a cape as part of it or associated with it.
-
C.
isOnCape
Indicates that one entity is located on or attached to the cape (a garment or geographic feature) of another entity.
-
D.
associatedWithCape
Indicates a relationship in which an entity is connected or linked in some way to a cape, such as by location, feature, or relevance.
-
E.
hasCasque
Indicates that one entity possesses, wears, or is equipped with a casque (a type of helmet or protective headgear).
- F. None of above.
Provenance (3 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 28, 2026, 12:43 a.m.