Triple
T32189206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roark family |
E822190
|
entity |
| Predicate | influenceOver |
P6148
|
FINISHED |
| Object | police of Basin 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: police of Basin City | Statement: [Roark family, influenceOver, police of Basin City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceOver Context triple: [Roark family, influenceOver, police of Basin City]
-
A.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
B.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
C.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
D.
politicalInfluenceIn
chosen
Indicates that an entity exerts or holds political influence within a specified place, jurisdiction, or political context.
-
E.
administrativeInfluenceOn
Indicates that one entity has the authority or capacity to affect, direct, or shape the administration, management, or governance 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 12:35 a.m.