Triple
T4293027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Hamilton (name) |
E99639
|
entity |
| Predicate | isCombinationOf |
P3980
|
FINISHED |
| Object | biblical given name and Scottish surname |
—
|
LITERAL 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: biblical given name and Scottish surname | Statement: [Thomas Hamilton (name), isCombinationOf, biblical given name and Scottish surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCombinationOf Context triple: [Thomas Hamilton (name), isCombinationOf, biblical given name and Scottish surname]
-
A.
isSubtractiveCombination
Indicates that one entity is formed or derived by subtracting one or more components, values, or parts of another entity.
-
B.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
C.
originalCombinationFor
Indicates that one entity is the initial or source combination from which another combined entity is derived or constructed.
-
D.
isComposite
chosen
Indicates that an entity is made up of multiple components or parts combined into a single whole.
-
E.
isTrimOf
Indicates that one entity is a version of another with leading and/or trailing whitespace characters removed.
- F. None of above.
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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35082228081908504e3fd7c4ca1e8 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.