Triple
T32612256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Wilson |
E833684
|
entity |
| Predicate | typeOfProspector |
P94712
|
FINISHED |
| Object | gold prospector |
—
|
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: gold prospector | Statement: [Jack Wilson, typeOfProspector, gold prospector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProspector Context triple: [Jack Wilson, typeOfProspector, gold prospector]
-
A.
estimatedNumberOfProspectors
Indicates the approximate count of individuals expected or believed to be prospectors in a given context.
-
B.
seekerType
Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
-
C.
personType
chosen
Indicates that an entity is classified as a particular type or category of person.
-
D.
roleInGoldRush
Indicates that an entity played a specific role or had a particular involvement in the historical event known as the Gold Rush.
-
E.
surveyor
Indicates that an entity performs the role or action of surveying, typically by measuring, inspecting, or assessing something such as land, structures, or conditions.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 1, 2026, 1:06 a.m.