Triple
T23000288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DataCite metadata schema |
E572613
|
entity |
| Predicate | supportsRelationType |
P150599
|
FINISHED |
| Object | IsCitedBy |
—
|
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: IsCitedBy | Statement: [DataCite metadata schema, supportsRelationType, IsCitedBy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRelationType Context triple: [DataCite metadata schema, supportsRelationType, IsCitedBy]
-
A.
supportsRelation
Indicates that one entity provides assistance, endorsement, or structural backing to another entity or its activity.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
supportsRuleType
Indicates that one entity is capable of handling, applying, or being compatible with a specified type of rule.
-
D.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
E.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18352bcf48190bd474eff69b3465b |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.