Triple
T2192828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John H. Lawrence |
E49901
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Lawrence |
E180561
|
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: Lawrence | Statement: [John H. Lawrence, hasFamilyName, Lawrence]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lawrence Context triple: [John H. Lawrence, hasFamilyName, Lawrence]
-
A.
Lawrence
Lawrence is the formal given name of Larry Ellison, the billionaire co-founder and longtime leader of Oracle Corporation.
-
B.
Lawrence
Lawrence is a historic mill city in northeastern Massachusetts that developed as a major textile manufacturing center along the Merrimack River.
-
C.
Lawrence
Lawrence is a city located within Marion County in the U.S. state of Indiana.
-
D.
Lawrence
chosen
Lawrence is a masculine given name of English origin, derived from the Latin "Laurentius" meaning "from Laurentum" or "crowned with laurel."
-
E.
Winfield
Winfield is a masculine given name most notably borne by 19th-century American military leader Winfield Scott.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf4a542881908aaaf4f0f85bc32c |
completed | March 7, 2026, 6:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5db283cc8190b75870cb2aabc5af |
completed | March 9, 2026, 5:42 a.m. |
Created at: March 4, 2026, 7:46 p.m.