Triple
T22977467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue |
E571364
|
entity |
| Predicate | districtRoleBeforeGames |
P150472
|
FINISHED |
| Object | orchard worker |
—
|
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: orchard worker | Statement: [Rue, districtRoleBeforeGames, orchard worker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtRoleBeforeGames Context triple: [Rue, districtRoleBeforeGames, orchard worker]
-
A.
districtRole
Indicates that an entity holds a specific role, function, or position within a particular district.
-
B.
leagueSystemRole
Indicates the specific role or function an entity holds within a league’s organizational or competitive system.
-
C.
cityStadiumRole
Indicates that a city serves a particular role or function in relation to a stadium, such as hosting, owning, or being the primary location for it.
-
D.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
E.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
- F. None of above. chosen
Provenance (4 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:48 p.m.