Triple
T33284623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadling |
E852145
|
entity |
| Predicate | settingCreatedBy |
P188968
|
FINISHED |
| Object | L. Frank Baum |
—
|
NE NERFINISHED |
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: L. Frank Baum | Statement: [Quadling, settingCreatedBy, L. Frank Baum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingCreatedBy Context triple: [Quadling, settingCreatedBy, L. Frank Baum]
-
A.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
B.
currentCreatedBy
Indicates that the entity represents the creator or originator of the current item, resource, or record.
-
C.
creatorOfSetting
Indicates that one entity is the originator or designer of the environment, context, or backdrop in which another entity exists or an event takes place.
-
D.
cardinalCreatedBy
Indicates that a cardinal (a high-ranking clergy member) was created or appointed by a specific authority or person.
-
E.
setInUniverseCreatedBy
chosen
Indicates that the narrative or setting of one entity takes place within a fictional universe that was originally created by another entity.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 1:32 a.m.