Triple
T13105082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Angeles |
E310823
|
entity |
| Predicate | hasGovernmentTypeInFiction |
P66248
|
FINISHED |
| Object | highly regulated society |
—
|
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: highly regulated society | Statement: [San Angeles, hasGovernmentTypeInFiction, highly regulated society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentTypeInFiction Context triple: [San Angeles, hasGovernmentTypeInFiction, highly regulated society]
-
A.
governedByFictional
Indicates that one entity is under the rule, control, or authority of another entity that is fictional or exists only in an imagined context.
-
B.
polityInFictionalWorld
Indicates that a political entity exists within, or is part of, a fictional world or universe.
-
C.
hasGovernmentTypeCountry
chosen
Indicates that a country possesses or is characterized by a particular form or type of government.
-
D.
hasFictionalLeader
Indicates that an entity is led or governed by a leader who is a fictional character rather than a real person.
-
E.
hasFictionalEstablishmentType
Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98154c9f48190aeca779d97151759 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.