Triple
T11985291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caterpillar |
E285260
|
entity |
| Predicate | givesProphecy |
P102738
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Caterpillar, givesProphecy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesProphecy Context triple: [Caterpillar, givesProphecy, yes]
-
A.
basedOnProphecyBy
Indicates that something occurs, is created, or is decided as a result of guidance, information, or prediction given by a particular prophecy or prophet.
-
B.
containsProphecyAbout
Indicates that one entity includes or conveys a prediction or foretelling specifically concerning another entity.
-
C.
interpretedAsProphecyBy
Indicates that something (such as an event, statement, or sign) is understood or treated by someone as a prophecy or predictive message about the future.
-
D.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
E.
prophecyCreator
Indicates that one entity is the originator or author of a given prophecy concerning another entity or event.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.