Triple
T4649429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XENPAK |
E102254
|
entity |
| Predicate | sizeComparison |
P23282
|
FINISHED |
| Object | larger than XFP |
—
|
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: larger than XFP | Statement: [XENPAK, sizeComparison, larger than XFP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeComparison Context triple: [XENPAK, sizeComparison, larger than XFP]
-
A.
scaleComparison
chosen
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
B.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
C.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
D.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
-
E.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.