Triple
T36913963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Layman |
E912991
|
entity |
| Predicate | workContextExplores |
P94403
|
FINISHED |
| Object | race |
—
|
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: race | Statement: [Layman, workContextExplores, race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workContextExplores Context triple: [Layman, workContextExplores, race]
-
A.
workExplores
chosen
Indicates that a work investigates, examines, or delves into a particular subject, theme, or concept.
-
B.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
C.
primaryWorkContext
Indicates the main environment, setting, or domain in which an entity typically performs its work or primary activities.
-
D.
nationalContextOfWork
Indicates the country or national setting within which the work or activity is carried out.
-
E.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.