Triple
T20480187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arp |
E502429
|
entity |
| Predicate | compilerField |
P140265
|
FINISHED |
| Object | extragalactic astronomy |
—
|
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: extragalactic astronomy | Statement: [Arp, compilerField, extragalactic astronomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilerField Context triple: [Arp, compilerField, extragalactic astronomy]
-
A.
compilerType
Indicates the specific kind or category of compiler associated with or used by an entity.
-
B.
compilerMethod
Indicates that a method is used by or generated for the compiler as part of the code compilation process.
-
C.
isFixedFieldOf
Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
-
D.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
-
E.
compilerRegion
Indicates a relationship where a code element is associated with, or belongs to, a specific region or segment as defined by the compiler.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:34 a.m.