Triple
T9752615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dim |
E236476
|
entity |
| Predicate | sizeRelativeToOtherBugs |
P23282
|
FINISHED |
| Object | large |
—
|
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: large | Statement: [Dim, sizeRelativeToOtherBugs, large]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeRelativeToOtherBugs Context triple: [Dim, sizeRelativeToOtherBugs, large]
-
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.
smallSizeIssuesStart
Indicates that problems or complications begin to occur when something is of a small size.
-
C.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
D.
sizeRelativeToCourt
Indicates how the size of an entity compares to the size of a court.
-
E.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fae332c8190b11f0258b5a5ae2b |
completed | April 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.