Triple
T29722186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M.52 |
E752085
|
entity |
| Predicate | hasWorkNumberType |
P191794
|
FINISHED |
| Object | M-number |
—
|
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: M-number | Statement: [M.52, hasWorkNumberType, M-number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkNumberType Context triple: [M.52, hasWorkNumberType, M-number]
-
A.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
B.
hasWorkIdentity
Indicates that an entity possesses a specific professional or occupational identity within a work-related context.
-
C.
hasWorkTypeRelation
Indicates a relationship specifying the type or category of work associated with an entity.
-
D.
hasVocalNumberType
Indicates that there is a specified type or category describing the number of vocal parts or voices involved in the relationship or action.
-
E.
hasWorkField
Indicates that an entity is associated with or operates within a particular field or area of work.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 28, 2026, 7:37 p.m.