Triple
T26586842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatinga |
E667232
|
entity |
| Predicate | phenomenonCharacteristics |
P72546
|
FINISHED |
| Object | birds fall to the ground |
—
|
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: birds fall to the ground | Statement: [Jatinga, phenomenonCharacteristics, birds fall to the ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phenomenonCharacteristics Context triple: [Jatinga, phenomenonCharacteristics, birds fall to the ground]
-
A.
examplePhenomenon
Indicates a representative or illustrative occurrence used to demonstrate or clarify a broader phenomenon or pattern.
-
B.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
C.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
D.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
primaryCharacteristics
chosen
Indicates the main defining traits or features that most fundamentally characterize an 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:06 a.m.