Triple
T22512699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Labors of Esfandiyar |
E556560
|
entity |
| Predicate | hasNumberOfLabors |
P148663
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Seven Labors of Esfandiyar, hasNumberOfLabors, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfLabors Context triple: [Seven Labors of Esfandiyar, hasNumberOfLabors, 7]
-
A.
laborNumber
Indicates a relationship where a specific labor or work assignment is identified or referenced by a unique number.
-
B.
hasManualLabor
Indicates that one entity performs or is responsible for physical or manual work in relation to another entity or context.
-
C.
chronologicalPositionInLabors
Indicates the specific order or sequence in which a given labor occurs within a defined series of labors.
-
D.
labourNumber
Indicates the identifier or count assigned to a specific unit of labor or work activity associated with an entity.
-
E.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d61a27881909faed490d2b65f39 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:50 p.m.