Triple
T28693208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Wells |
E729341
|
entity |
| Predicate | foundObjectType |
P188423
|
FINISHED |
| Object | rough diamond |
—
|
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: rough diamond | Statement: [Frederick Wells, foundObjectType, rough diamond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundObjectType Context triple: [Frederick Wells, foundObjectType, rough diamond]
-
A.
givenObjectType
Indicates that an entity is assigned, provides, or is associated with a specific type of object.
-
B.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
C.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
-
D.
guardedObjectType
Indicates that something serves as the type or category of object that is being guarded or protected in the relationship.
-
E.
oreType
Indicates the specific kind or classification of ore associated with an 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 28, 2026, 5:37 a.m.