Triple
T4293650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nomad |
E99655
|
entity |
| Predicate | hasContributorOccupation |
P30146
|
FINISHED |
| Object | actor |
—
|
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: actor | Statement: [The Nomad, hasContributorOccupation, actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContributorOccupation Context triple: [The Nomad, hasContributorOccupation, actor]
-
A.
authorOccupation
Indicates the professional role or job that an author holds or is associated with.
-
B.
isAssociatedWithProfessionOfBearer
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
-
C.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
-
D.
hasContributionFrom
chosen
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
E.
representedOccupation
Indicates that one entity has served as an official or formal representative of another entity’s occupation or professional role.
- 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.