Triple
T33519067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flick |
E858450
|
entity |
| Predicate | hasFlowFactor |
P178373
|
FINISHED |
| Object | free |
—
|
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: free | Statement: [Flick, hasFlowFactor, free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlowFactor Context triple: [Flick, hasFlowFactor, free]
-
A.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
B.
hasFillingFactor
Indicates that one entity is associated with a specific filling factor value characterizing how fully a space, volume, or capacity is occupied.
-
C.
hasFlowForm
Indicates that one entity possesses or is associated with a particular configuration, pattern, or form of flow (such as fluid, data, or traffic movement).
-
D.
hasDirectionOfFlow
Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
-
E.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:39 a.m.