Triple
T22040152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reddit Gold |
E544315
|
entity |
| Predicate | technicalDomain |
P19268
|
FINISHED |
| Object | web service feature |
—
|
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: web service feature | Statement: [Reddit Gold, technicalDomain, web service feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technicalDomain Context triple: [Reddit Gold, technicalDomain, web service feature]
-
A.
technicalCrux
Indicates a key technical challenge or bottleneck that critically determines the feasibility or success of a solution or system.
-
B.
technicalType
Indicates the specific technical category or classification that characterizes how something is implemented, structured, or functions.
-
C.
technologyField
chosen
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
-
D.
technicalAlliance
Indicates a collaborative relationship where entities formally cooperate and share expertise, resources, or technology to achieve mutual technical goals.
-
E.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f532b08190be80c5af039b4c29 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.