Triple
T12792045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koki |
E305789
|
entity |
| Predicate | hasRealWorldOrigin |
P106938
|
FINISHED |
| Object | created by an unknown author |
—
|
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: created by an unknown author | Statement: [Koki, hasRealWorldOrigin, created by an unknown author]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealWorldOrigin Context triple: [Koki, hasRealWorldOrigin, created by an unknown author]
-
A.
hasRealWorldVersion
Indicates that something has a corresponding or equivalent version that exists in the real, physical world.
-
B.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
-
D.
hasManMadeOrigin
Indicates that something originates from or is created by human activity rather than occurring naturally.
-
E.
hasRealModel
Indicates that an abstract, theoretical, or simplified entity is associated with a corresponding concrete or physically instantiated model in the real world.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6b55248190ab938e69eb263612 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:30 p.m.