Triple
T29169672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise |
E739421
|
entity |
| Predicate | featuresAggressiveFlow |
P178373
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Paradise, featuresAggressiveFlow, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAggressiveFlow Context triple: [Paradise, featuresAggressiveFlow, true]
-
A.
hasFlowFactor
chosen
Indicates that one entity is associated with a specific flow-related characteristic, parameter, or influence that affects how something moves, transfers, or progresses between or within entities.
-
B.
featuresThreat
Indicates that one entity includes, presents, or contains a threat associated with another entity.
-
C.
flowVariation
Indicates how the rate or pattern of flow (such as water, traffic, or data) changes over time or across different conditions.
-
D.
flowsVia
Indicates that something (such as a substance, signal, or current) moves or is transmitted along, through, or by means of a specified medium, path, or channel.
-
E.
flareActivity
Indicates that an entity exhibits or undergoes a sudden increase or burst in activity, intensity, or prominence.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: April 28, 2026, 11:52 a.m.