Triple
T19327160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tree |
E483389
|
entity |
| Predicate | hasSubjectMatterForm |
P135620
|
FINISHED |
| Object | non-figurative |
—
|
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: non-figurative | Statement: [The Tree, hasSubjectMatterForm, non-figurative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectMatterForm Context triple: [The Tree, hasSubjectMatterForm, non-figurative]
-
A.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
B.
hadBusinessForm
Indicates that an entity possessed or utilized a particular business form or organizational structure in the context of its activities or operations.
-
C.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
D.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
E.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6163e3a5081909195192356bcebc3 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:33 p.m.