Triple
T32615370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facial Action Coding System |
E833769
|
entity |
| Predicate | intensityRange |
P1942
|
FINISHED |
| Object | A to E |
—
|
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: A to E | Statement: [Facial Action Coding System, intensityRange, A to E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intensityRange Context triple: [Facial Action Coding System, intensityRange, A to E]
-
A.
intensityScale
chosen
Indicates the degree or level of strength, magnitude, or severity associated with an event, property, or measurement, typically according to a defined scale.
-
B.
luminanceRange
Indicates the span between the minimum and maximum luminance (brightness) values associated with an entity or visual element.
-
C.
brightnessRangeClass
Indicates the classification of an entity based on the range or interval of its brightness values.
-
D.
pixelValueRange
Indicates the allowable or actual minimum-to-maximum range of pixel intensity values associated with an image or image region.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:06 a.m.