Triple
T3770698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semper Augustus |
E82789
|
entity |
| Predicate | causeOfPattern |
P708
|
FINISHED |
| Object | tulip breaking virus |
—
|
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: tulip breaking virus | Statement: [Semper Augustus, causeOfPattern, tulip breaking virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPattern Context triple: [Semper Augustus, causeOfPattern, tulip breaking virus]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
C.
factPattern
Indicates that a specific configuration of facts or circumstances holds in a situation, typically used as the basis for applying rules, reasoning, or legal/logic inferences.
-
D.
hasCause
chosen
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
E.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc307cf8819090730b5e697bb197 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.