Triple
T31585466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown’s Schoolhouse community |
E805944
|
entity |
| Predicate | localInfluenceExertedBy |
P89454
|
FINISHED |
| Object | Brown family |
—
|
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: Brown family | Statement: [Brown’s Schoolhouse community, localInfluenceExertedBy, Brown family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localInfluenceExertedBy Context triple: [Brown’s Schoolhouse community, localInfluenceExertedBy, Brown family]
-
A.
nearbyInfluence
Indicates that one entity affects or exerts influence on another due to being physically or spatially close to it.
-
B.
hasLocalImpact
chosen
Indicates that an entity produces effects or consequences within a specific local area or community.
-
C.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
D.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
E.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 30, 2026, 10:25 p.m.