Triple
T9022846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lerna |
E215768
|
entity |
| Predicate | hydraLabourNumber |
P59642
|
FINISHED |
| Object | second labour |
—
|
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: second labour | Statement: [Lerna, hydraLabourNumber, second labour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydraLabourNumber Context triple: [Lerna, hydraLabourNumber, second labour]
-
A.
labourNumber
chosen
Indicates the identifier or count assigned to a specific unit of labor or work activity associated with an entity.
-
B.
laborNumber
Indicates a relationship where a specific labor or work assignment is identified or referenced by a unique number.
-
C.
hrNumber
Indicates a unique human resources identification number assigned to an individual or position within an organization.
-
D.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
E.
laborSystem
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a454b808190af6bb48f7a4da917 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.