Triple
T34948230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Work |
E1007911
|
entity |
| Predicate | hasLevelOfAbstraction |
P144628
|
FINISHED |
| Object | Higher than expression |
—
|
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: Higher than expression | Statement: [Work, hasLevelOfAbstraction, Higher than expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelOfAbstraction Context triple: [Work, hasLevelOfAbstraction, Higher than expression]
-
A.
architectureLevel
Indicates the relative layer or tier an entity occupies within an architectural structure or system design.
-
B.
hasStructureLevel
chosen
Indicates a relationship where one entity possesses, is assigned, or is characterized by a particular structural level within a hierarchy or layered organization.
-
C.
hasObservationLevel
Indicates the degree, intensity, or extent to which something is observed, monitored, or measured within a given context.
-
D.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
E.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4 p.m.