Triple
T18104109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dong Maeng |
E433304
|
entity |
| Predicate | scaleComparedToPredecessors |
P23282
|
FINISHED |
| Object | smaller |
—
|
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: smaller | Statement: [Dong Maeng, scaleComparedToPredecessors, smaller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleComparedToPredecessors Context triple: [Dong Maeng, scaleComparedToPredecessors, smaller]
-
A.
comparedToPredecessor
Indicates that something is being evaluated or measured in relation to the thing that came immediately before it.
-
B.
scaleComparison
chosen
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
C.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
-
D.
detailLevelComparedToPredecessor
Indicates how the level of detail of an entity compares to that of its immediate predecessor (e.g., more detailed, less detailed, or similar).
-
E.
emissionsComparedToPredecessor
Indicates how the emissions of an entity compare in magnitude (e.g., higher, lower, or equal) to those of its immediate predecessor.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb8dd308190a9c98ac2b1d8b872 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.