Triple
T10328841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CountQueuingStrategy |
E242827
|
entity |
| Predicate | highWaterMarkType |
P38256
|
FINISHED |
| Object | number |
—
|
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: number | Statement: [CountQueuingStrategy, highWaterMarkType, number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highWaterMarkType Context triple: [CountQueuingStrategy, highWaterMarkType, number]
-
A.
highWaterMarkLocation
Indicates the specific place where the highest level reached by water is or was observed.
-
B.
highestPart
Indicates that one entity is the topmost or uppermost portion of another entity.
-
C.
typeOfLimit
chosen
Indicates that one entity specifies the category or kind of limit that applies to another entity.
-
D.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
E.
higherFormationType
Indicates that one entity is classified as a broader or more inclusive formation type that encompasses or organizes the other 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.