Triple
T38309511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regor (cut-down) |
E1033645
|
entity |
| Predicate | isCutDownFrom |
P58367
|
FINISHED |
| Object | dual-core Regor |
—
|
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: dual-core Regor | Statement: [Regor (cut-down), isCutDownFrom, dual-core Regor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCutDownFrom Context triple: [Regor (cut-down), isCutDownFrom, dual-core Regor]
-
A.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
B.
cutDown
chosen
Indicates that an agent causes something standing or elevated (such as a tree or structure) to fall or be reduced by cutting.
-
C.
hasCut
Indicates that one entity has made or possesses a cut in, on, or through another entity.
-
D.
cutFrom
Indicates that one entity has been removed or separated from another entity by cutting.
-
E.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.