Triple
T35929731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pool B |
E1039124
|
entity |
| Predicate | levelRelativeToPoolA |
P25304
|
FINISHED |
| Object | one level below |
—
|
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: one level below | Statement: [Pool B, levelRelativeToPoolA, one level below]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelRelativeToPoolA Context triple: [Pool B, levelRelativeToPoolA, one level below]
-
A.
levelWithinPME
Indicates that one entity’s level or degree is contained within, or falls under, the scope of another entity’s Project Management Environment (PME) level.
-
B.
relativeLevel
chosen
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
C.
levels
Indicates that one entity adjusts, equalizes, or smooths out the height, intensity, or degree of another entity.
-
D.
levelManaged
Indicates that one entity is responsible for overseeing, controlling, or maintaining a particular level, degree, or tier associated with another entity.
-
E.
levelInNorthAmericanSystem
Indicates that an entity’s level or grade is defined according to the standards or structure used in the North American system.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.