Triple
T19745824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piers Sellers |
E474247
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Piers |
E155806
|
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: Piers | Statement: [Piers Sellers, givenName, Piers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piers Context triple: [Piers Sellers, givenName, Piers]
-
A.
Piers
chosen
Piers is a masculine given name of English origin, historically used as a medieval form of Peter and borne by various notable figures in literature and public life.
-
B.
Piers 1–2
Piers 1–2 are key berthing facilities within Honolulu Harbor that serve commercial and maritime operations in Honolulu, Hawaii.
-
C.
Piersonn
Piersonn is a variant spelling of the surname Pierson, which is of English and French origin and typically means "son of Piers" or "son of Peter."
-
D.
G Pier
G Pier is one of the passenger boarding concourses at Amsterdam Airport Schiphol, serving multiple gates for international flights.
-
E.
Piers 24–28
Piers 24–28 are a group of commercial and maritime docking facilities within Honolulu Harbor in Honolulu, Hawaii.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529387ac819094e4d66d630e8b98 |
completed | April 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07b501e7348190bf2b14c98cd7cdb0 |
completed | May 16, 2026, 12:06 a.m. |
Created at: April 10, 2026, 1:47 p.m.