Triple
T38515248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Luck |
E922324
|
entity |
| Predicate | hiredTo |
P83995
|
FINISHED |
| Object | defend a Mexican village |
—
|
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: defend a Mexican village | Statement: [Harry Luck, hiredTo, defend a Mexican village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiredTo Context triple: [Harry Luck, hiredTo, defend a Mexican village]
-
A.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
B.
employedTo
chosen
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
C.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
-
D.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
E.
employedUnder
Indicates that one entity works as an employee under the authority, supervision, or organizational structure of another entity.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.