Triple
T1982785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assembly Floor Analysis Unit |
E43065
|
entity |
| Predicate | workProductType |
P1366
|
FINISHED |
| Object | floor analysis reports |
—
|
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: floor analysis reports | Statement: [Assembly Floor Analysis Unit, workProductType, floor analysis reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workProductType Context triple: [Assembly Floor Analysis Unit, workProductType, floor analysis reports]
-
A.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
B.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
C.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
D.
workModel
Indicates that one entity serves as, or is based on, a particular model used for work, operation, or functional behavior.
-
E.
partOfWorkType
Indicates that something is a component, subtype, or specific category within a broader type of work.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.