Triple
T27737603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.RuntimeType |
E697566
|
entity |
| Predicate | underlyingTypeFor |
P32473
|
FINISHED |
| Object | System.Type |
—
|
NE NERFINISHED |
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: System.Type | Statement: [System.RuntimeType, underlyingTypeFor, System.Type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingTypeFor Context triple: [System.RuntimeType, underlyingTypeFor, System.Type]
-
A.
inferredType
Indicates that an entity has a type or category that has been deduced or derived rather than explicitly stated.
-
B.
hasUnderlyingEntity
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
-
C.
underlyingRelation
Indicates that one entity serves as a fundamental basis, cause, or support for another entity or relationship.
-
D.
baseType
chosen
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
E.
ultimateType
Indicates that one entity is the final, most specific, or resolved type/classification of another entity in a type hierarchy or typing process.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 3:13 p.m.