Triple
T32536440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun RPC |
E831601
|
entity |
| Predicate | xdrExpansion |
P174561
|
FINISHED |
| Object | External Data Representation |
—
|
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: External Data Representation | Statement: [Sun RPC, xdrExpansion, External Data Representation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: xdrExpansion Context triple: [Sun RPC, xdrExpansion, External Data Representation]
-
A.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
B.
restrictedExpansionOf
Indicates a relationship where one entity is an expansion of another, but with added constraints or limitations that make it more specific or narrowly applicable than the original.
-
C.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
D.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
E.
expansionNumber
Indicates the specific expansion sequence or identifier assigned to an entity within a series of related additions or extensions.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57062c481908b041788842c5990 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:01 a.m.