Triple
T22133644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ii |
E546968
|
entity |
| Predicate | hasNameFeature |
P75425
|
FINISHED |
| Object | one of the shortest place names in the world |
—
|
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: one of the shortest place names in the world | Statement: [Ii, hasNameFeature, one of the shortest place names in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameFeature Context triple: [Ii, hasNameFeature, one of the shortest place names in the world]
-
A.
hasNameCharacteristic
chosen
Indicates that an entity possesses a specific quality or attribute related to its name.
-
B.
hasNamesakeFeature
Indicates that one entity has a feature (such as a place, object, or structure) that is named after another entity.
-
C.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
D.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
E.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b81d5c819085fd18bf3ae28333 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.