Triple
T35161941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brook Neal |
E1015289
|
entity |
| Predicate | likelyRole |
P28456
|
FINISHED |
| Object | early settler |
—
|
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: early settler | Statement: [Brook Neal, likelyRole, early settler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyRole Context triple: [Brook Neal, likelyRole, early settler]
-
A.
possibleRole
chosen
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d2c63408190aa9a1bfc18a3e021 |
completed | May 3, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.