Triple
T10248236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | able rate |
E240273
|
entity |
| Predicate | experienceRequirement |
P72224
|
FINISHED |
| Object | more experience than ordinary seaman |
—
|
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: more experience than ordinary seaman | Statement: [able rate, experienceRequirement, more experience than ordinary seaman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experienceRequirement Context triple: [able rate, experienceRequirement, more experience than ordinary seaman]
-
A.
appointmentRequirement
Indicates that a particular action, service, or interaction can only occur if an appointment has been scheduled or a specified appointment condition is met.
-
B.
recruitmentRequirement
chosen
Indicates that a certain condition, qualification, or criterion must be satisfied for an entity to be eligible for recruitment or hiring.
-
C.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
D.
workRequirement
Indicates that one entity imposes or specifies a condition related to work that another entity must fulfill.
-
E.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:27 a.m.