Triple
T14957635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Princess and the Pea |
E372971
|
entity |
| Predicate | testObject |
P102649
|
FINISHED |
| Object | a pea |
—
|
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: a pea | Statement: [The Princess and the Pea, testObject, a pea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testObject Context triple: [The Princess and the Pea, testObject, a pea]
-
A.
testObjective
Indicates that an entity serves as the goal, purpose, or intended outcome of a test or testing activity.
-
B.
testElement
chosen
Indicates that an entity is an element used for testing, experimentation, or validation within a system or process.
-
C.
testsSubject
Indicates that one entity administers or performs a test or examination on another entity as its subject.
-
D.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
E.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cc73848190ac181782b20dc838 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.