Triple
T16478943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beni Isguen |
E400264
|
entity |
| Predicate | socialRule |
P113726
|
FINISHED |
| Object | regulated access for outsiders |
—
|
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: regulated access for outsiders | Statement: [Beni Isguen, socialRule, regulated access for outsiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialRule Context triple: [Beni Isguen, socialRule, regulated access for outsiders]
-
A.
communicationRule
Indicates a rule or constraint that governs how communication between entities should occur.
-
B.
generalRule
chosen
Indicates that something functions as a broad, overarching principle or guideline that applies across multiple specific cases or situations.
-
C.
socialComposition
Indicates the makeup or distribution of different social groups or categories within a population or community.
-
D.
sharesRulesWith
Indicates that two entities follow, are governed by, or operate under the same set of rules or regulations.
-
E.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01230881908b2147a25f78b7f4 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.