Triple
T35008172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump City Zoo |
E1009868
|
entity |
| Predicate | hasPopularityInUniverse |
P100387
|
FINISHED |
| Object | popular attraction in Jump 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: popular attraction in Jump City | Statement: [Jump City Zoo, hasPopularityInUniverse, popular attraction in Jump City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularityInUniverse Context triple: [Jump City Zoo, hasPopularityInUniverse, popular attraction in Jump City]
-
A.
inUniversePopularity
chosen
Indicates how popular or well-known an entity is within the fictional universe or setting it belongs to.
-
B.
inUniverseFame
Indicates that an entity is famous or widely recognized within the fictional universe or narrative world it belongs to.
-
C.
isGloballyPopular
Indicates that something is widely recognized, liked, or used by people across many different countries or regions.
-
D.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
E.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 3, 2026, 4:01 p.m.