Triple
T503001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Houston |
E10439
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Samuel |
E18206
|
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: Samuel | Statement: [Sam Houston, givenName, Samuel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samuel Context triple: [Sam Houston, givenName, Samuel]
-
A.
Samuel
chosen
Samuel is a masculine given name of Hebrew origin meaning "name of God" or "God has heard," widely used across many cultures and languages.
-
B.
Samuel
Samuel is the birth name of the famed American author Mark Twain, known for classics like "The Adventures of Tom Sawyer" and "Adventures of Huckleberry Finn."
-
C.
Benjamin
Benjamin is the given name of Benjamin "Bugsy" Siegel, the notorious American mobster who played a key role in the development of Las Vegas.
-
D.
Jonathan
Jonathan is a common masculine given name of Hebrew origin, meaning "Yahweh has given."
-
E.
Edwin
Edwin is a masculine given name of Old English origin meaning "rich friend" or "prosperous friend."
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1357738819085eae6c10fa2fca9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4b8a96a188190b7a6be463de3d736 |
completed | March 1, 2026, 10:07 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.