Triple
T38645053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsair |
E938692
|
entity |
| Predicate | microIntensive |
P132991
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Corsair, microIntensive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: microIntensive Context triple: [Corsair, microIntensive, true]
-
A.
miniaturizedIn
Indicates that one entity exists as a smaller-scale or reduced-size version within or relative to another entity.
-
B.
minorProduction
Indicates that an entity is involved in a secondary or less significant production activity relative to a primary production process.
-
C.
intensiveUse
chosen
Indicates a relationship where an entity is used in a concentrated, frequent, or high-intensity manner by another entity.
-
D.
miniaturizedBy
Indicates that an entity has been made smaller in size or scale by another entity or process.
-
E.
microRequirement
Indicates a fine-grained or very small-scale requirement that must be satisfied within a larger specification or system.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.