Triple
T22987690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Strang |
E571956
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Strang |
—
|
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: Strang | Statement: [John Strang, hasFamilyName, Strang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strang Context triple: [John Strang, hasFamilyName, Strang]
-
A.
Strang
chosen
Strang is a surname of likely Germanic or Scandinavian origin, sometimes used as a variant of "Strong."
-
B.
Stange
Stange is a rural municipality in Innlandet county, Norway, known for its agricultural landscape and proximity to the town of Hamar.
-
C.
Strawn
Strawn is a surname and place name of English and Scottish origin, often considered a variant of the name Strachan.
-
D.
Strank
Strank is a surname most notably associated with Michael Strank, one of the U.S. Marines immortalized in the iconic World War II photograph of the flag raising on Iwo Jima.
-
E.
Strachane
Strachane is an alternative spelling of the Scottish surname Strachan, historically associated with a clan and place in Aberdeenshire, Scotland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829b4ea88190bc1a01183df7a1bb |
completed | April 29, 2026, 4:01 a.m. |
Created at: April 17, 2026, 3:49 p.m.