Triple
T21066424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debye length |
E518984
|
entity |
| Predicate | isLongWhen |
P142712
|
FINISHED |
| Object | plasma density is low |
—
|
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: plasma density is low | Statement: [Debye length, isLongWhen, plasma density is low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongWhen Context triple: [Debye length, isLongWhen, plasma density is low]
-
A.
hasLong
Indicates that an entity possesses or exhibits a great extent or duration in some measurable dimension (such as length or time).
-
B.
isLongOnlyEligible
Indicates that an entity is permitted to take only long (buy) positions and is not allowed to establish short (sell) positions.
-
C.
isLongRunning
Indicates that an action, process, or operation continues for an extended duration, typically longer than is usual or expected.
-
D.
hasLongStretchIn
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
-
E.
isElongatedDueTo
Indicates that one entity becomes longer in shape, form, or duration specifically as a result of the influence or effect of another entity or factor.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb455fc81909cc63fa0e87b6a35 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:45 p.m.