Triple
T8219724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fog City |
E192026
|
entity |
| Predicate | alsoKnownForCity |
P81686
|
FINISHED |
| Object | mountain city |
—
|
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: mountain city | Statement: [Fog City, alsoKnownForCity, mountain city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoKnownForCity Context triple: [Fog City, alsoKnownForCity, mountain city]
-
A.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
-
B.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
C.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
D.
performedInCity
Indicates that an action, event, or performance took place within the boundaries of a specified city.
-
E.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7772b76c8190b1952650c736eb91 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4d9b03108190a6785834f21ff75e |
completed | March 31, 2026, 4:29 a.m. |
Created at: March 30, 2026, 5:45 p.m.