Triple
T35304291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump City Mall |
E1019590
|
entity |
| Predicate | ownedByInUniverse |
P62301
|
FINISHED |
| Object | unidentified corporate owner |
—
|
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: unidentified corporate owner | Statement: [Jump City Mall, ownedByInUniverse, unidentified corporate owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedByInUniverse Context triple: [Jump City Mall, ownedByInUniverse, unidentified corporate owner]
-
A.
ownedByFictionalCharacter
chosen
Indicates that something is possessed or owned by a fictional (not real-world) character.
-
B.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
C.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
D.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
-
E.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904d95b48190b98dca59dbb592d8 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.