Triple
T38528567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agnew family (local settlers) |
E923296
|
entity |
| Predicate | nameDerivedFor |
P36773
|
FINISHED |
| Object | Agnew Meadows |
—
|
NE NERFINISHED |
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: Agnew Meadows | Statement: [Agnew family (local settlers), nameDerivedFor, Agnew Meadows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDerivedFor Context triple: [Agnew family (local settlers), nameDerivedFor, Agnew Meadows]
-
A.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, another entity.
-
B.
commonNameDerivedFrom
Indicates that the commonly used name of one entity originates from, or is derived based on, another entity.
-
C.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
D.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
nameComesFrom
chosen
Indicates that the name or designation of one entity is derived from, inspired by, or based on 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:32 p.m.