Triple
T25425448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLMUL |
E637104
|
entity |
| Predicate | carriesHandled |
P159117
|
FINISHED |
| Object | no integer carries (carry-less) |
—
|
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: no integer carries (carry-less) | Statement: [CLMUL, carriesHandled, no integer carries (carry-less)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriesHandled Context triple: [CLMUL, carriesHandled, no integer carries (carry-less)]
-
A.
carriedFor
Indicates that one entity transported or bore another entity on behalf of or for the benefit of that other entity.
-
B.
instrumentHandled
Indicates that an entity uses, operates, or physically manipulates an instrument or tool to perform an action or task.
-
C.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
D.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
E.
usedToHandle
Indicates that one entity previously managed, processed, or dealt with another entity as part of its function or role.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bfdb748190abfd40ed1838d9aa |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:57 p.m.