Triple
T23036839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Fry |
E573619
|
entity |
| Predicate | usedInventionOf |
P150739
|
FINISHED |
| Object | office organization |
—
|
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: office organization | Statement: [Arthur Fry, usedInventionOf, office organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInventionOf Context triple: [Arthur Fry, usedInventionOf, office organization]
-
A.
basedOnInventionOf
Indicates that something is derived from, developed using, or fundamentally relies on a particular invention.
-
B.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
C.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
D.
inventionType
Indicates the specific category or kind of invention that characterizes the relationship between an invention and its type.
-
E.
hasInventionProperty
Indicates that an entity possesses a specific characteristic, attribute, or quality related to an invention.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1850fe5348190b42259595d82cff4 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:53 p.m.