Triple
T20453354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moss (2022) |
E501710
|
entity |
| Predicate | hasRuntimeCategory |
P140157
|
FINISHED |
| Object | short |
—
|
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: short | Statement: [Moss (2022), hasRuntimeCategory, short]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuntimeCategory Context triple: [Moss (2022), hasRuntimeCategory, short]
-
A.
hasCategorySystem
Indicates that an entity is associated with or organized according to a particular categorization system.
-
B.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
-
C.
hasPrimaryRuntime
Indicates that an entity is associated with a main or default runtime environment it primarily uses or depends on.
-
D.
hasFunctionCategory
Indicates that something is associated with a particular functional category or role it performs.
-
E.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d039af08190827bf765b50515a8 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:32 a.m.