Triple
T4659982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selenites |
E102504
|
entity |
| Predicate | societalControl |
P58265
|
FINISHED |
| Object | strict regulation of individual roles |
—
|
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: strict regulation of individual roles | Statement: [Selenites, societalControl, strict regulation of individual roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: societalControl Context triple: [Selenites, societalControl, strict regulation of individual roles]
-
A.
institutionalControl
Indicates that one institution has governing, regulatory, or managerial authority over another entity or activity.
-
B.
politicalControl
Indicates that one entity holds governing authority, influence, or decision-making power over the political actions or structure of another entity.
-
C.
hasViewOnSociety
Indicates that an entity holds a particular perspective, opinion, or stance regarding society or social structures.
-
D.
examinesSociety
Indicates that one entity studies, analyzes, or critically investigates the structure, norms, and dynamics of a society.
-
E.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6328387c81909a500e694a739e6e |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:15 p.m.