Triple
T380619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candidate Recommendation |
E8669
|
entity |
| Predicate | typicallyPrecedes |
P97
|
FINISHED |
| Object | wider deployment of the technology |
—
|
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: wider deployment of the technology | Statement: [Candidate Recommendation, typicallyPrecedes, wider deployment of the technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyPrecedes Context triple: [Candidate Recommendation, typicallyPrecedes, wider deployment of the technology]
-
A.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
B.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
C.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
D.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
E.
predecessorHoliday
Indicates that one holiday directly precedes another in a temporal or calendrical sequence.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2c95088190a603bb1ee076ebd6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.