Triple
T12373515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scherrie Payne |
E295061
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Payne |
E791810
|
NE 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: Payne | Statement: [Scherrie Payne, familyName, Payne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Payne Context triple: [Scherrie Payne, familyName, Payne]
-
A.
Payne
Payne is a residential and light commercial heating and cooling equipment brand owned by Carrier Corporation, known for offering budget-friendly HVAC systems.
-
B.
Payne
Payne is a small community located within Bibb County in the state of Georgia, United States.
-
C.
Payne
Payne is a given name most notably associated with members of the prominent American Whitney family, including philanthropist Payne Whitney.
-
D.
Payne
chosen
Payne is a common English surname of Norman origin, historically derived from the medieval given name "Pagan" or "Payne."
-
E.
T. Payne
T. Payne was an 18th-century London bookseller and publisher known for issuing significant works of political and philosophical thought.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62ac1e82c8190abb46ca5799e6680 |
completed | May 2, 2026, 4:48 p.m. |
Created at: April 8, 2026, 9:54 p.m.