Triple
T26966737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP |
E679190
|
entity |
| Predicate | complementClass |
P138848
|
FINISHED |
| Object | coRP |
—
|
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: coRP | Statement: [RP, complementClass, coRP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complementClass Context triple: [RP, complementClass, coRP]
-
A.
complementOf
chosen
Indicates that one entity serves as a complement to another, completing or specifying it in a grammatical or semantic relationship.
-
B.
complement
Indicates that one entity completes, enhances, or makes another entity whole or more effective by providing what it lacks.
-
C.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
D.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
E.
combiningClass
Indicates that one entity functions as a combining diacritic or mark that attaches to a base character, specifying how it combines in text rendering or encoding.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 6:36 a.m.